summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorFrediano Ziglio <frediano.ziglio@cloud.com>2024-06-19 11:40:15 +0100
committerJuergen Gross <jgross@suse.com>2024-07-02 09:35:52 +0200
commitad162488bbd359abda99c9819f5cbe9172f40935 (patch)
tree0e71a3c292c989a119a09ac82abfa59ba10bbcb8
parente51d31c454fbd64e5de8d85c94bb519228f4c78a (diff)
downloadlinux-ad162488bbd359abda99c9819f5cbe9172f40935.tar.gz
linux-ad162488bbd359abda99c9819f5cbe9172f40935.tar.bz2
linux-ad162488bbd359abda99c9819f5cbe9172f40935.zip
x86/xen/time: Reduce Xen timer tick
Current timer tick is causing some deadline to fail. The current high value constant was probably due to an old bug in the Xen timer implementation causing errors if the deadline was in the future. This was fixed in Xen commit: 19c6cbd90965 xen/vcpu: ignore VCPU_SSHOTTMR_future Usage of VCPU_SSHOTTMR_future in Linux kernel was removed by: c06b6d70feb3 xen/x86: don't lose event interrupts Signed-off-by: Frediano Ziglio <frediano.ziglio@cloud.com> Reviewed-by: Juergen Gross <jgross@suse.com> Link: https://lore.kernel.org/r/20240619104015.30477-1-frediano.ziglio@cloud.com Signed-off-by: Juergen Gross <jgross@suse.com>
-rw-r--r--arch/x86/xen/time.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
index 52fa5609b7f6..96521b1874ac 100644
--- a/arch/x86/xen/time.c
+++ b/arch/x86/xen/time.c
@@ -30,7 +30,7 @@
#include "xen-ops.h"
/* Minimum amount of time until next clock event fires */
-#define TIMER_SLOP 100000
+#define TIMER_SLOP 1
static u64 xen_sched_clock_offset __read_mostly;