Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1628379 > unrolled thread

[PATCH 1/9] x86/tsc: Provide tsc=unstable boot parameter

Started byPeter Zijlstra <peterz@infradead.org>
First post2017-04-21 19:10 +0200
Last post2017-04-21 19:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [PATCH 1/9] x86/tsc: Provide tsc=unstable boot parameter Peter Zijlstra <peterz@infradead.org> - 2017-04-21 19:10 +0200

#1628379 — [PATCH 1/9] x86/tsc: Provide tsc=unstable boot parameter

FromPeter Zijlstra <peterz@infradead.org>
Date2017-04-21 19:10 +0200
Subject[PATCH 1/9] x86/tsc: Provide tsc=unstable boot parameter
Message-ID<tyKef-8vc-57@gated-at.bofh.it>
Since the clocksource watchdog will only detect broken TSC after the
fact, all TSC based clocks will likely have observed non-continuous
values before/when switching away from TSC.

Therefore only thing to fully avoid random clock movement when your
BIOS randomly mucks with TSC values from SMI handlers is reporting the
TSC as unstable at boot.

Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
---
 arch/x86/kernel/tsc.c |    2 ++
 1 file changed, 2 insertions(+)

--- a/arch/x86/kernel/tsc.c
+++ b/arch/x86/kernel/tsc.c
@@ -374,6 +374,8 @@ static int __init tsc_setup(char *str)
 		tsc_clocksource_reliable = 1;
 	if (!strncmp(str, "noirqtime", 9))
 		no_sched_irq_time = 1;
+	if (!strcmp(str, "unstable"))
+		mark_tsc_unstable("boot parameter");
 	return 1;
 }
 

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web