From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Cc: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: [PATCH 7/10] linux 2.6.18: time handling
Date: Tue, 06 Mar 2007 11:38:04 +0000 [thread overview]
Message-ID: <C213031C.AAEE%keir@xensource.com> (raw)
In-Reply-To: <45EC0A4C.76E4.0078.0@novell.com>
On 5/3/07 11:17, "Jan Beulich" <jbeulich@novell.com> wrote:
> Remove struct timer_opts left-overs, add a Xen clocksource, and adjust
> conditionals for x86-64.
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
The other issue afaics is that the clocksource simply does raw reads of the
TSC, subsequently scaled by cpu_khz. This isn't very accurate and will cause
horrible problems if some CPUs enter power-saving modes (not explicitly
supported yet, but can happen due to auto thermal throttling) or on bigger
systems where TSCs may not be driven from the same mainboard clock (and
hence will drift).
I think Jeremy Fitzhardinge has an alternative clocksource patch which iirc
is more in line with how Xen time works (should advertise a GHz frequency
clocksource, and do scaling of the TSC value according to time-record values
read from shared_info). Having thought about this some more I think
clocksource support is worth getting into our tree, but let's look at both
available patches and decide which is the better basis for further work.
Jeremy: If I'm not mistaken and you do have a patch floating around, could
you post it?
Thanks,
Keir
next prev parent reply other threads:[~2007-03-06 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 11:17 [PATCH 7/10] linux 2.6.18: time handling Jan Beulich
2007-03-05 15:03 ` Keir Fraser
2007-03-05 15:09 ` Jan Beulich
2007-03-05 15:20 ` Keir Fraser
2007-03-06 11:38 ` Keir Fraser [this message]
2007-03-06 15:50 ` Jeremy Fitzhardinge
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=C213031C.AAEE%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=jeremy@goop.org \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.