From: Peter Zijlstra <peterz@infradead.org>
To: tglx@linutronix.de, mingo@kernel.org, rafael@kernel.org,
nmorey@kalray.eu
Cc: srinivas.pandruvada@linux.intel.com,
jacob.jun.pan@linux.intel.com, linux-kernel@vger.kernel.org,
peterz@infradead.org
Subject: [RFC][PATCH 0/4] sched_clock vs TSC wreckage
Date: Thu, 15 Dec 2016 14:04:54 +0100 [thread overview]
Message-ID: <20161215130454.914605806@infradead.org> (raw)
A few weeks ago Nicolas reported some impressive TSC wreckage on his i7-3820
running on an AsusTek Rampage IV Gene board [*].
These are a few patches that should hopefully allow us to do better in the face
of such 'creativity'.
[*] to be fair, Asus did in fact release a BIOS update that fixes this issue.
next reply other threads:[~2016-12-15 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 13:04 Peter Zijlstra [this message]
2016-12-15 13:04 ` [RFC][PATCH 1/4] clocksource: Add optional cs::mark_unstable() method Peter Zijlstra
2016-12-15 13:04 ` [RFC][PATCH 2/4] sched/clock: Update static_key usage Peter Zijlstra
2016-12-15 13:04 ` [RFC][PATCH 3/4] sched/clock: Delay switching sched_clock to stable Peter Zijlstra
2016-12-15 13:04 ` [RFC][PATCH 4/4] sched/clock: Provide better clock continuity Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161215130454.914605806@infradead.org \
--to=peterz@infradead.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=nmorey@kalray.eu \
--cc=rafael@kernel.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®