From: Thomas Gleixner <tglx@linutronix.de>
To: sroland@vmware.com
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Roland Scheidegger <rscheidegger_lists@hispeed.ch>
Subject: Re: [PATCH] x86/tsc: RFC: re-synchronize TSCs to boot cpu TSC
Date: Thu, 8 Dec 2016 08:56:48 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1612080854420.3400@nanos> (raw)
In-Reply-To: <1481179042-968-1-git-send-email-sroland@vmware.com>
On Thu, 8 Dec 2016, sroland@vmware.com wrote:
> From: Roland Scheidegger <rscheidegger_lists@hispeed.ch>
>
> Some bios (Dell T5810 here) mess up the perfectly synced TSCs on boot
> and resume (probably trying to set some continuous time, but writing
> TSC directly instead of TSC_ADJUST which can only result in failure).
> This will cause the kernel to reject the tsc as clocksource due to
> the detected time warp.
> Try to fix this up by syncing the TSCs of non-boot cpus to the boot
> cpu, both on boot and resume.
> I've got some use case here which relies on really fast time
> measurements, without TSCs things run noticeably slower (ok the
> measurements probably are excessive) (and the timing information is
> probably useless too without TSCs).
> (This is quite a big hack, I have no idea what happens with
> multi-socket systems for instance, but it near certainly won't be
> right. I really don't know what I'm doing here, it is not a proper
> patch but a working (for me) proof-of-concept hack I've been using
> since a while although actually only with kernel 4.4 - I suppose
> some proper quirk would be needed. I guess there's also some chance
> SMM in general could do further damage to TSCs sometimes making this
> hack fail.)
Can you please try
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/timers
which contains a solution to this problem.
Thanks,
tglx
next parent reply other threads:[~2016-12-08 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1481179042-968-1-git-send-email-sroland@vmware.com>
2016-12-08 7:56 ` Thomas Gleixner [this message]
[not found] ` <6194ea73-99dd-ceca-6f8d-e945ca717c75@hispeed.ch>
2016-12-09 9:59 ` Thomas Gleixner
2016-12-09 16:46 ` Roland Scheidegger
2016-12-09 17:33 ` Thomas Gleixner
2016-12-09 20:50 ` Roland Scheidegger
2016-12-09 22:59 ` Thomas Gleixner
2016-12-10 1:55 ` Roland Scheidegger
2016-12-10 5:20 ` Roland Scheidegger
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=alpine.DEB.2.20.1612080854420.3400@nanos \
--to=tglx@linutronix.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rscheidegger_lists@hispeed.ch \
--cc=sroland@vmware.com \
--cc=x86@kernel.org \
/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®