rtc,x86: CMOS RTC fixes
Subsystems (3)
v2 cover rtc,x86: CMOS RTC fixes
Hello,
This patch series fixes some issues in the RTC CMOS handling code.
First three patches fix bugs in drivers/rtc:
1. Fix rtc_lock usage in cmos_set_alarm() in rtc-cmos.c.
2. Do not touch RTC alarm registers when the RTC update is in progress. (On some Intel chipsets, this causes bogus values being read or writes to fail silently.)
3. Fix presence check of the RTC CMOS: the clock was misdetected as broken on one of my systems.
Patches 1 and 2 are Cced stable. I'm going to submit patch 3 manually to stable after some regression testing in master.
Last three patches contain fixes for arch/x86/rtc.c: duplicate code removal and a renaming of a function. I'd prefer that they be merged together with patch nr 3.
I'm also considering whether function x86_wallclock_init() in arch/x86/kernel/x86_init.c should call mc146818_does_rtc_work() to make sure that the CMOS RTC is present and behaves itself. This might be useful.
Patch nr 7:
Revert "rtc: cmos: Replace spin_lock_irqsave with spin_lock in hard IRQ"
was made obsolete by mainlining of
commit 13be2efc390a ("rtc: cmos: Disable irq around direct invocation of cmos_interrupt()")
so I've dropped it from this series.
This is my first patch series, so please review carefully.
Greetings,
Mateusz
PATCH RESEND v2 1/6 rtc-cmos: take rtc_lock while reading from CMOS
Reading from the CMOS involves writing to the index register and then reading from the data register. Therefore access to the CMOS has to be serialized with the rtc_lock. This invocation of CMOS_READ was not serialized, which could cause trouble when other code is accessing CMOS at the same time.
Use spin_lock_irq() like the rest of the function.
Nothing in kernel modifies the RTC_DM_BINARY bit, so there could be a separate pair of spin_lock_irq() / spin_unlock_irq() before doing the math.
--- drivers/rtc/rtc-cmos.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/rtc/rtc-cmos.c +3 -0
@@ -463,7 +463,10 @@ static int cmos_set_alarm(struct device *dev, struct rtc_wkalrm *t) min = t->time.tm_min; sec = t->time.tm_sec; +spin_lock_irq (&rtc_lock); rtc_control =CMOS_READ (RTC_CONTROL ); +spin_unlock_irq (&rtc_lock); +if (!(rtc_control &RTC_DM_BINARY ) ||RTC_ALWAYS_BCD ) {/* Writing 0xff means "don't care" or "match all". */ mon = (mon <=12 ) ?bin2bcd (mon) :0xff ;
Signature · 1 line
2.25.1
PATCH RESEND v2 2/6 rtc-cmos: dont touch alarm registers during update
In reply to Mateusz JończykSome Intel chipsets disconnect the time and date RTC registers when the clock update is in progress: during this time reads may return bogus values and writes fail silently. This includes the RTC alarm registers.
[1]
cmos_read_alarm() and cmos_set_alarm() did not take account for that, which caused alarm time reads to sometimes return bogus values. This can be shown with a test patch that I am attaching to this patch series. Setting the alarm clock also probably did fail sometimes.
To make this patch suitable for inclusion in stable kernels, I'm using a simple method for avoiding the RTC update cycle. This method is used in mach_set_rtc_mmss() in arch/x86/kernel/rtc.c. A more elaborate algorithm
- as in mc146818_get_time() in drivers/rtc/rtc-mc146818-lib.c - would be too complcated for stable. [2]
cmos_wait_for_uip_clear() has the rtc_lock taken while waiting for the UIP bit to become clear. This should be harmless as during the UIP the RTC cannot be read from anyway. mach_get_cmos_time() in arch/x86/kernel/rtc.c does things the same way.
[1] 7th Generation Intel ® Processor Family I/O for U/Y Platforms [...] Datasheet, Volume 1 of 2 (Intel's Document Number: 334658-006) Page 208
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/7th-and-8th-gen-core-family-mobile-u-y-processor-lines-i-o-datasheet-vol-1.pdf
"If a RAM read from the ten time and date bytes is attempted during an update cycle, the value read do not necessarily represent the true contents of those locations. Any RAM writes under the same conditions are ignored.'
[2] I'm going to submit a unification patch for a later kernel release - prefer to see this in stable.
--- drivers/rtc/rtc-cmos.c | 38 ++++++++++++++++++++++++++++++++++++-- 1 file changed, 36 insertions(+), 2 deletions(-)
drivers/rtc/rtc-cmos.c +36 -2
@@ -248,6 +248,31 @@ static int cmos_set_time(struct device *dev, struct rtc_time *t)return mc146818_set_time (t); } +/* Some Intel chipsets disconnect the alarm registers when the clock update is +* in progress - during this time reads return bogus values and writes may fail +* silently. See for example "7th Generation Intel® Processor Family I/O for +* U/Y Platforms [...] Datasheet", section 27.7.1 +* +* Check the UIP bit to prevent this, waiting for max 10ms for it to become +* clear. +* +* This function has to be called with rtc_lock taken. +*/ +static int cmos_wait_for_uip_clear (struct device *dev) +{ +int i; + +for (i =0 ; i <100 ; i++) { +if ((CMOS_READ (RTC_FREQ_SELECT ) &RTC_UIP ) ==0 ) +return 0 ; +udelay (100 ); + } + +dev_warn_ratelimited (dev,"UIP bit is stuck, cannot access RTC registers\n" ); + +return 1 ; +} +static int cmos_read_alarm (struct device *dev,struct rtc_wkalrm *t) {struct cmos_rtc *cmos =dev_get_drvdata (dev);
@@ -257,12 +282,17 @@ static int cmos_read_alarm(struct device *dev, struct rtc_wkalrm *t)if (!is_valid_irq (cmos->irq))return -EIO ; +spin_lock_irq (&rtc_lock); + +if (cmos_wait_for_uip_clear (dev)) { +spin_unlock_irq (&rtc_lock); +return -EIO ; + } +/* Basic alarms only support hour, minute, and seconds fields. * Some also support day and month, for alarms up to a year in * the future. */ - -spin_lock_irq (&rtc_lock); t->time.tm_sec =CMOS_READ (RTC_SECONDS_ALARM ); t->time.tm_min =CMOS_READ (RTC_MINUTES_ALARM ); t->time.tm_hour =CMOS_READ (RTC_HOURS_ALARM );
@@ -477,6 +507,10 @@ static int cmos_set_alarm(struct device *dev, struct rtc_wkalrm *t) }spin_lock_irq (&rtc_lock); +if (cmos_wait_for_uip_clear (dev)) { +spin_unlock_irq (&rtc_lock); +return -EIO ; + }/* next rtc irq must not be from previous alarm setting */ cmos_irq_disable (cmos,RTC_AIE );
Signature · 1 line
2.25.1
PATCH 1/1 rtc-cmos: cmos_read_alarm bug demonstration
Before my commit "rtc-cmos: dont touch alarm registers during update", applying this patch and reading the CMOS time like so:
while true; do cat /sys/class/rtc/rtc0/time ; sleep 0.5; done
produces errors in dmesg.
--- drivers/rtc/rtc-cmos.c | 61 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 61 insertions(+)
drivers/rtc/rtc-cmos.c +61 -0
@@ -43,6 +43,9 @@#include <linux/dmi.h> #endif +#include <linux/ktime.h> +#include <linux/timekeeping.h> +/* this is for "generic access to PC-style RTC" using CMOS_READ/CMOS_WRITE */ #include <linux/mc146818rtc.h>
@@ -220,6 +223,8 @@ static inline void cmos_write_bank2(unsigned char val, unsigned char addr)/*----------------------------------------------------------------*/ +static void cmos_read_alarm_uip_debugging (struct device *dev); +static int cmos_read_time (struct device *dev,struct rtc_time *t) {/*
@@ -234,6 +239,8 @@ static int cmos_read_time(struct device *dev, struct rtc_time *t)* That'll make Y3K compatility (year > 2070) easy! */ mc146818_get_time (t); + +cmos_read_alarm_uip_debugging (dev);return 0 ; }
@@ -348,6 +355,60 @@ static int cmos_read_alarm(struct device *dev, struct rtc_wkalrm *t)return 0 ; } +static void cmos_read_alarm_uip_debugging (struct device *dev) +{ +unsigned long flags; +unsigned char rtc_uip_baseline, rtc_uip; +struct rtc_wkalrm t_baseline, t; +ktime_t time_start, time_end; +int i; + +spin_lock_irqsave (&rtc_lock, flags); + rtc_uip_baseline =CMOS_READ (RTC_FREQ_SELECT ) &RTC_UIP ; +spin_unlock_irqrestore (&rtc_lock, flags); + +cmos_read_alarm (dev, &t_baseline); + + time_start =ktime_get (); + +for (i =0 ; i <2000 ; i++) { +spin_lock_irqsave (&rtc_lock, flags); + rtc_uip =CMOS_READ (RTC_FREQ_SELECT ) &RTC_UIP ; +spin_unlock_irqrestore (&rtc_lock, flags); + +cmos_read_alarm (dev, &t); + +if (t_baseline.time.tm_sec != t.time.tm_sec) { +dev_err (dev, +"Inconsistent alarm tm_sec value: %d != %d (RTC_UIP = %d; %d)\n" , + t_baseline.time.tm_sec, + t.time.tm_sec, + rtc_uip_baseline, rtc_uip); + } +if (t_baseline.time.tm_min != t.time.tm_min) { +dev_err (dev, +"Inconsistent alarm tm_min value: %d != %d (RTC_UIP = %d; %d)\n" , + t_baseline.time.tm_min, + t.time.tm_min, + rtc_uip_baseline, rtc_uip); + } +if (t_baseline.time.tm_hour != t.time.tm_hour) { +dev_err (dev, +"Inconsistent alarm tm_hour value: %d != %d (RTC_UIP = %d; %d)\n" , + t_baseline.time.tm_hour, + t.time.tm_hour, + rtc_uip_baseline, rtc_uip); + } + + } + + time_end =ktime_get (); + +pr_info_ratelimited ("%s: loop executed in %lld ns\n" , + __func__,ktime_to_ns (ktime_sub (time_end, time_start))); +} + +static void cmos_checkintr (struct cmos_rtc *cmos,unsigned char rtc_control) {unsigned char rtc_intr;
Signature · 1 line
2.25.1
Greg KH
maintainerRe: [PATCH RESEND 2/6] rtc-cmos: dont touch alarm registers during update
In reply to Mateusz JończykQuoted 10 lines · Mateusz Jończyk
Some Intel chipsets disconnect the time and date RTC registers when the clock update is in progress: during this time reads may return bogus values and writes fail silently. This includes the RTC alarm registers.
[1]
cmos_read_alarm()andcmos_set_alarm()did not take account for that, which caused alarm time reads to sometimes return bogus values. This can be shown with a test patch that I am attaching to this patch series. Setting the alarm clock also probably did fail sometimes.
Quoted 5 lines
To make this patch suitable for inclusion in stable kernels, I'm using a simple method for avoiding the RTC update cycle. This method is used in
mach_set_rtc_mmss()inarch/x86/kernel/rtc.c. A more elaborate algorithm
- as inmc146818_get_time()indrivers/rtc/rtc-mc146818-lib.c- would be too complcated for stable. [2]
No, just do it properly the first time, do not worry about stable kernels, we can just take the also-correct version for backporting if needed.
thanks,
greg k-h
PATCH RESEND v2 3/6 rtc-mc146818-lib: fix RTC presence check
In reply to Mateusz JończykTo prevent an infinite loop in mc146818_get_time(),
commit 211e5db19d15 ("rtc: mc146818: Detect and handle broken RTCs") added a check for RTC availability. Together with a later fix, it checked if bit 6 in register 0x0d is cleared. This, however, caused a false negative on a motherboard with an AMD SB710 southbridge; according to the specification [1], bit 6 of register 0x0d of this chipset is a scratchbit.
This caused a regression in Linux 5.11 - the RTC was determined broken by the kernel and not used by rtc-cmos.c [3].
As a better alternative, check whether the UIP ("Update-in-progress") bit is set for longer then 10ms. If that is the case, then apparently the RTC is either absent (and all register reads return 0xff) or broken. Also limit the number of loop iterations in mc146818_get_time() to 10.
In a previous approach to this problem, I implemented a check whether the RTC_HOURS register contains a value <= 24. This, however, sometimes did not work correctly on my Intel Kaby Lake laptop. According to Intel's documentation [2], "the time and date RAM locations (0-9) are disconnected from the external bus" during the update cycle so reading this register without checking the UIP bit is incorrect.
[1] AMD SB700/710/750 Register Reference Guide, page 308,
https://developer.amd.com/wordpress/media/2012/10/43009_sb7xx_rrg_pub_1.00.pdf
[2] 7th Generation Intel ® Processor Family I/O for U/Y Platforms [...] Datasheet Volume 1 of 2, page 209
Intel's Document Number: 334658-006,
https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/7th-and-8th-gen-core-family-mobile-u-y-processor-lines-i-o-datasheet-vol-1.pdf
[3] Functions in arch/x86/kernel/rtc.c apparently were using it.
--- drivers/rtc/rtc-cmos.c | 10 ++++------ drivers/rtc/rtc-mc146818-lib.c | 34 ++++++++++++++++++++++++++++++---- include/linux/mc146818rtc.h | 1 + 3 files changed, 35 insertions(+), 10 deletions(-)
v2: Tweak commit description, remove "Cc: stable" (I'll send it manually after more regression testing).
drivers/rtc/rtc-cmos.c +4 -6
@@ -833,16 +833,14 @@ cmos_do_probe(struct device *dev, struct resource *ports, int rtc_irq)rename_region (ports,dev_name (&cmos_rtc.rtc->dev)); -spin_lock_irq (&rtc_lock); - -/* Ensure that the RTC is accessible. Bit 6 must be 0! */ -if ((CMOS_READ (RTC_VALID ) &0x40 ) !=0 ) { -spin_unlock_irq (&rtc_lock); -dev_warn (dev,"not accessible\n" ); +if (!mc146818_does_rtc_work ()) { +dev_warn (dev,"broken or not accessible\n" ); retval = -ENXIO ; goto cleanup1; } +spin_lock_irq (&rtc_lock); +if (!(flags &CMOS_RTC_FLAGS_NOFREQ )) {/* force periodic irq to CMOS reset default of 1024Hz; *
drivers/rtc/rtc-mc146818-lib.c +30 -4
@@ -8,10 +8,35 @@#include <linux/acpi.h> #endif +/* +* If the UIP (Update-in-progress) bit of the RTC is set for more then +* 10ms, the RTC apparently is broken or not present. +*/ +unsigned int mc146818_does_rtc_work (void ) +{ +int i; +unsigned char val; +unsigned long flags; + +for (i =0 ; i <20 ; i++) { +spin_lock_irqsave (&rtc_lock, flags); + val =CMOS_READ (RTC_FREQ_SELECT ); +spin_unlock_irqrestore (&rtc_lock, flags); + +if ((val &RTC_UIP ) ==0 ) +return 1 ; + +udelay (500 ); + } + +return 0 ; +} +unsigned int mc146818_get_time (struct rtc_time *time) {unsigned char ctrl;unsigned long flags; +unsigned int iter_count =0 ;unsigned char century =0 ;bool retry;
@@ -20,13 +45,14 @@ unsigned int mc146818_get_time(struct rtc_time *time)#endif again: -spin_lock_irqsave (&rtc_lock, flags); -/* Ensure that the RTC is accessible. Bit 6 must be 0! */ -if (WARN_ON_ONCE ((CMOS_READ (RTC_VALID ) &0x40 ) !=0 )) { -spin_unlock_irqrestore (&rtc_lock, flags); +if (iter_count >10 ) { +pr_err_ratelimited ("Unable to read current time from RTC\n" );memset (time,0xff ,sizeof (*time));return 0 ; } + iter_count++; + +spin_lock_irqsave (&rtc_lock, flags);/* * Check whether there is an update in progress during which the
include/linux/mc146818rtc.h +1 -0
@@ -123,6 +123,7 @@ struct cmos_rtc_board_info {#define RTC_IO_EXTENT_USED RTC_IO_EXTENT#endif /* ARCH_RTC_LOCATION */ +unsigned int mc146818_does_rtc_work (void );unsigned int mc146818_get_time (struct rtc_time *time);int mc146818_set_time (struct rtc_time *time);
Signature · 1 line
2.25.1
PATCH RESEND v2 4/6 rtc-mc146818-lib: reduce RTC_UIP polling period
In reply to Mateusz JończykA shorter period makes mc146818_get_time() more similar to mach_get_cmos_time() in arch/x86/kernel/rtc.c, which performs the same function, but is busy waiting for the RTC_UIP bit to clear.
Waiting 1ms every time is not necessary, for example on some AMD boxes the RTC_UIP bit is documented as being high for around 270 microseconds in some cases [1], which agreed with experiments on an SB710 southbridge. So 100us seems optimal.
[1] AMD SB700/710/750 Register Reference Guide, page 307,
https://developer.amd.com/wordpress/media/2012/10/43009_sb7xx_rrg_pub_1.00.pdf
"SB700 A12: The UIP high pulse is 270 μS Typical when SS on SRC clock is OFF and 100μ min when SRC SS is ON." [sic]
--- drivers/rtc/rtc-mc146818-lib.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/rtc/rtc-mc146818-lib.c +3 -3
@@ -45,7 +45,7 @@ unsigned int mc146818_get_time(struct rtc_time *time)#endif again: -if (iter_count >10 ) { +if (iter_count >100 ) {pr_err_ratelimited ("Unable to read current time from RTC\n" );memset (time,0xff ,sizeof (*time));return 0 ;
@@ -57,7 +57,7 @@ unsigned int mc146818_get_time(struct rtc_time *time)/* * Check whether there is an update in progress during which the * readout is unspecified. The maximum update time is ~2ms. Poll -* every msec for completion. +* every 100 usec for completion. * * Store the second value before checking UIP so a long lasting NMI * which happens to hit after the UIP check cannot make an update
@@ -67,7 +67,7 @@ unsigned int mc146818_get_time(struct rtc_time *time)if (CMOS_READ (RTC_FREQ_SELECT ) &RTC_UIP ) {spin_unlock_irqrestore (&rtc_lock, flags); -mdelay (1 ); +udelay (100 ); goto again; }
Signature · 1 line
2.25.1
PATCH RESEND v2 5/6 x86/rtc: mach_get_cmos_time - rm duplicated code
In reply to Mateusz JończykThere are functions in drivers/rtc/rtc-mc146818-lib.c that handle reading from / writing to the CMOS RTC clock. mach_get_cmos_time() in arch/x86/kernel/rtc.c did not use them and was mostly a duplicate of mc146818_get_time(). Modify mach_get_cmos_time() to use mc146818_get_time() and remove the duplicated code.
mach_get_cmos_time() used a different algorithm than mc146818_get_time(), but these functions are equivalent. The major differences are:
- mc146818_get_time() is better refined: it was updated in commit 05a0302c3548 ("rtc: mc146818: Prevent reading garbage") to take account of various edge conditions,
- when the UIP ("Update in progress") bit of the RTC is set, mach_get_cmos_time() was busy waiting with cpu_relax() while mc146818_get_time() is now using udelay(100) in every loop iteration,
- mach_get_cmos_time() assumed that the RTC year must be >= 2000, which may not be true on some old boxes with a dead battery.
The RTC writing counterpart, mach_set_rtc_mmss() is already using mc146818_get_time() from drivers/rtc. This was done in
commit 3195ef59cb42 ("x86: Do full rtc synchronization with ntp")
It appears that mach_get_cmos_time() was simply forgotten.
--- arch/x86/kernel/rtc.c | 55 +++++-------------------------------------- 1 file changed, 6 insertions(+), 49 deletions(-)
arch/x86/kernel/rtc.c +6 -49
@@ -20,15 +20,12 @@/* * This is a special lock that is owned by the CPU and holds the index * register we are working with. It is required for NMI access to the -* CMOS/RTC registers. See include/asm-i386/mc146818rtc.h for details. +* CMOS/RTC registers. See arch/x86/include/asm/mc146818rtc.h for details. */ volatile unsigned long cmos_lock;EXPORT_SYMBOL (cmos_lock);#endif /* CONFIG_X86_32 */ -/* For two digit years assume time is always after that */ -#define CMOS_YEARS_OFFS 2000 -DEFINE_SPINLOCK (rtc_lock);EXPORT_SYMBOL (rtc_lock);
@@ -62,8 +59,7 @@ int mach_set_rtc_mmss(const struct timespec64 *now)void mach_get_cmos_time (struct timespec64 *now) { -unsigned int status, year, mon, day, hour, min, sec, century =0 ; -unsigned long flags; +struct rtc_time tm;/* * If pm_trace abused the RTC as storage, set the timespec to 0,
@@ -74,51 +70,12 @@ void mach_get_cmos_time(struct timespec64 *now)return ; } -spin_lock_irqsave (&rtc_lock, flags); - -/* -* If UIP is clear, then we have >= 244 microseconds before -* RTC registers will be updated. Spec sheet says that this -* is the reliable way to read RTC - registers. If UIP is set -* then the register access might be invalid. -*/ -while ((CMOS_READ (RTC_FREQ_SELECT ) &RTC_UIP )) -cpu_relax (); - - sec =CMOS_READ (RTC_SECONDS ); - min =CMOS_READ (RTC_MINUTES ); - hour =CMOS_READ (RTC_HOURS ); - day =CMOS_READ (RTC_DAY_OF_MONTH ); - mon =CMOS_READ (RTC_MONTH ); - year =CMOS_READ (RTC_YEAR ); - -#ifdef CONFIG_ACPI -if (acpi_gbl_FADT.header.revision >=FADT2_REVISION_ID && - acpi_gbl_FADT.century) - century =CMOS_READ (acpi_gbl_FADT.century); -#endif - - status =CMOS_READ (RTC_CONTROL ); -WARN_ON_ONCE (RTC_ALWAYS_BCD && (status &RTC_DM_BINARY )); - -spin_unlock_irqrestore (&rtc_lock, flags); - -if (RTC_ALWAYS_BCD || !(status &RTC_DM_BINARY )) { - sec =bcd2bin (sec); - min =bcd2bin (min); - hour =bcd2bin (hour); - day =bcd2bin (day); - mon =bcd2bin (mon); - year =bcd2bin (year); +if (!mc146818_get_time (&tm)) { + now->tv_sec = now->tv_nsec =0 ; +return ; } -if (century) { - century =bcd2bin (century); - year += century *100 ; - }else - year +=CMOS_YEARS_OFFS ; - - now->tv_sec =mktime64 (year, mon, day, hour, min, sec); + now->tv_sec =rtc_tm_to_time64 (&tm); now->tv_nsec =0 ; }
Signature · 1 line
2.25.1
PATCH RESEND v2 6/6 x86/rtc: rename mach_set_rtc_mmss
In reply to Mateusz JończykOnce upon a time, before
commit 3195ef59cb42 ("x86: Do full rtc synchronization with ntp") in 2013, the function set only the minute and seconds registers of the CMOS RTC. This is no longer true, so rename the function to mach_set_cmos_time.
--- arch/x86/include/asm/mc146818rtc.h | 2 +- arch/x86/kernel/rtc.c | 4 ++-- arch/x86/kernel/x86_init.c | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
arch/x86/include/asm/mc146818rtc.h +1 -1
@@ -95,7 +95,7 @@ static inline unsigned char current_lock_cmos_reg(void)unsigned char rtc_cmos_read (unsigned char addr);void rtc_cmos_write (unsigned char val,unsigned char addr); -extern int mach_set_rtc_mmss (const struct timespec64 *now); +extern int mach_set_cmos_time (const struct timespec64 *now);extern void mach_get_cmos_time (struct timespec64 *now);#define RTC_IRQ 8
arch/x86/kernel/rtc.c +2 -2
@@ -30,13 +30,13 @@ DEFINE_SPINLOCK(rtc_lock);EXPORT_SYMBOL (rtc_lock);/* -* In order to set the CMOS clock precisely, set_rtc_mmss has to be +* In order to set the CMOS clock precisely, mach_set_cmos_time has to be * called 500 ms after the second nowtime has started, because when * nowtime is written into the registers of the CMOS clock, it will * jump to the next second precisely 500 ms later. Check the Motorola * MC146818A or Dallas DS12887 data sheet for details. */ -int mach_set_rtc_mmss (const struct timespec64 *now) +int mach_set_cmos_time (const struct timespec64 *now) {unsigned long long nowtime = now->tv_sec;struct rtc_time tm;
arch/x86/kernel/x86_init.c +1 -1
@@ -133,7 +133,7 @@ struct x86_platform_ops x86_platform __ro_after_init = { .calibrate_cpu = native_calibrate_cpu_early, .calibrate_tsc = native_calibrate_tsc, .get_wallclock = mach_get_cmos_time, - .set_wallclock = mach_set_rtc_mmss, + .set_wallclock = mach_set_cmos_time, .iommu_shutdown = iommu_shutdown_noop, .is_untracked_pat_range = is_ISA_range, .nmi_init = default_nmi_init,
Signature · 1 line
2.25.1