From: Mike Galbraith <bitbucket@online.de>
To: Alex <xor@xor.bz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TSC Problems (warp between CPUs)
Date: Sat, 28 Dec 2013 05:02:52 +0100 [thread overview]
Message-ID: <1388203372.5387.85.camel@marge.simpson.net> (raw)
In-Reply-To: <b65bbca027bb2a473f989e60871c2dd2@xor.bz>
On Sat, 2013-12-28 at 13:24 +1100, Alex wrote:
> Linux does not write to the TSC since quite a while... which means the
> BIOS is doing that. It really should not.
I saw the same on an Intel server recently, poor thing was stuck with
using HPET.
-Mike
next prev parent reply other threads:[~2013-12-28 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 2:24 Alex
2013-12-28 4:02 ` Mike Galbraith [this message]
2013-12-28 9:51 ` Alex
2013-12-28 13:38 ` el_es
2013-12-28 14:35 ` One Thousand Gnomes
2013-12-29 0:21 ` Alex
2013-12-31 21:24 ` Alex
2014-10-07 10:19 ` Adrian Vasile
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=1388203372.5387.85.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=xor@xor.bz \
/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
Powered by JetHome