summaryrefslogtreecommitdiffstats
path: root/arch/x86/include/asm
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2021-05-16 09:42:13 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2021-05-16 09:42:13 -0700
commit8ce3648158d7bc9e5035d5a1db02c892905babbf (patch)
treec01f3911e705d9e4332a173ec0bce5d7d5252bea /arch/x86/include/asm
parentf44e58bb1905ada4910f26676d2ea22a35545276 (diff)
parent3486d2c9be652a31033363bdd50391b0c8a8fe21 (diff)
downloadlinux-stable-8ce3648158d7bc9e5035d5a1db02c892905babbf.tar.gz
linux-stable-8ce3648158d7bc9e5035d5a1db02c892905babbf.tar.bz2
linux-stable-8ce3648158d7bc9e5035d5a1db02c892905babbf.zip
Merge tag 'timers-urgent-2021-05-16' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull timer fixes from Thomas Gleixner: "Two fixes for timers: - Use the ALARM feature check in the alarmtimer core code insted of the old method of checking for the set_alarm() callback. Drivers can have that callback set but the feature bit cleared. If such a RTC device is selected then alarms wont work. - Use a proper define to let the preprocessor check whether Hyper-V VDSO clocksource should be active. The code used a constant in an enum with #ifdef, which evaluates to always false and disabled the clocksource for VDSO" * tag 'timers-urgent-2021-05-16' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: clocksource/drivers/hyper-v: Re-enable VDSO_CLOCKMODE_HVCLOCK on X86 alarmtimer: Check RTC features instead of ops
Diffstat (limited to 'arch/x86/include/asm')
-rw-r--r--arch/x86/include/asm/vdso/clocksource.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/arch/x86/include/asm/vdso/clocksource.h b/arch/x86/include/asm/vdso/clocksource.h
index 119ac8612d89..136e5e57cfe1 100644
--- a/arch/x86/include/asm/vdso/clocksource.h
+++ b/arch/x86/include/asm/vdso/clocksource.h
@@ -7,4 +7,6 @@
VDSO_CLOCKMODE_PVCLOCK, \
VDSO_CLOCKMODE_HVCLOCK
+#define HAVE_VDSO_CLOCKMODE_HVCLOCK
+
#endif /* __ASM_VDSO_CLOCKSOURCE_H */