From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Joanna Rutkowska <joanna@invisiblethingslab.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: A clocksource question
Date: Tue, 09 Mar 2010 15:36:09 -0800 [thread overview]
Message-ID: <4B96DB69.10101@goop.org> (raw)
In-Reply-To: <4B962748.90609@invisiblethingslab.com>
On 03/09/2010 02:47 AM, Joanna Rutkowska wrote:
> I would appreciate if somebody could shed some light on the currently
> preferred setting of the clocksource for the pvops0 kernels, used both
> in Dom0 and DomU (I'm using pvops0 in DomU because it provides backends,
> e.g. network backend).
>
clocksource=xen is supposed to be the ideal clocksource, with no downsides.
> I have a bad experience with running the Dom0 kernel
> (xen/stabale-2.6.31.6-based) with the default clocksource=xen, as it
> results in the system getting temporary "hangs", very short ones, but
> annoying. E.g. when one types fast on a keyboard, then every 10 seconds
> or so, the keystroke processing seems to be slowing down significantly
> for a second o so.
>
There have been a number of reports about hiccups of varying degrees of
severity when using clocksource=xen (and, interestingly, in KVM when
using its very similar pv clock interface). I haven't seen anyone
mention keyboard interactive performance; the failure mode I've seen is
disk IO hiccuping or even getting completely wedged. Unfortunately I
haven't made much headway in debugging it (or even reliably reproducing it).
What is the hardware platform? How many CPUs are you using? Does
pinning the vcpus to pcpus help?
> Running the kernel with clocksource=jiffies eliminates the above problem
> but has a disadvantage of the clock drift in Dom0. This is not
> acceptable on my setup, where I don't have any networking in Dom0, which
> means I cannot correct it via NTP.
>
> Interestingly the above problem didn't seem to affect the Dom0 kernel
> based on xen/stable-2.6.32.
That's interesting; there's no difference in the Xen-specific
timekeeping parts of the kernel, but perhaps something else has changed
in the way time is handled.
I don't remember if 3.4.2 ended up with tsc emulation, but if it does
you might try enabling it.
> Unfortunately I assume I'm no longer able to
> run this kernel when using Xen 3.4.2.
>
Yes. 3.4.3 will support the newer kernels, but that isn't released yet.
J
next prev parent reply other threads:[~2010-03-09 23:36 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 10:47 A clocksource question Joanna Rutkowska
2010-03-09 10:50 ` Keir Fraser
2010-03-09 10:54 ` Joanna Rutkowska
2010-03-09 11:06 ` Joanna Rutkowska
2010-03-09 12:07 ` Pasi Kärkkäinen
2010-03-09 12:10 ` Joanna Rutkowska
2010-03-09 15:42 ` Konrad Rzeszutek Wilk
2010-03-09 23:36 ` Jeremy Fitzhardinge [this message]
2010-03-10 22:13 ` Joanna Rutkowska
2010-03-11 0:07 ` Dan Magenheimer
2010-03-11 0:15 ` Joanna Rutkowska
2010-03-11 0:21 ` Ian Pratt
2010-03-11 0:44 ` Dan Magenheimer
2010-03-12 0:34 ` Joanna Rutkowska
2010-03-11 0:52 ` Joanna Rutkowska
2010-03-11 1:06 ` Jeremy Fitzhardinge
2010-03-11 1:19 ` Joanna Rutkowska
2010-03-11 4:55 ` Jeremy Fitzhardinge
2010-03-11 10:49 ` Joanna Rutkowska
2010-03-12 0:27 ` Joanna Rutkowska
2010-03-12 0:49 ` Jeremy Fitzhardinge
2010-03-12 0:38 ` Joanna Rutkowska
2010-03-12 19:02 ` Joanna Rutkowska
2010-03-12 21:24 ` Jeremy Fitzhardinge
2010-03-12 21:56 ` Tobias Geiger
2010-03-12 22:02 ` Jeremy Fitzhardinge
2010-03-12 21:01 ` Joanna Rutkowska
2010-03-12 21:13 ` Joanna Rutkowska
2010-03-12 23:48 ` Jeremy Fitzhardinge
2010-03-13 9:58 ` Joanna Rutkowska
2010-03-13 19:30 ` Jeremy Fitzhardinge
2010-03-15 6:49 ` Tobias Geiger
2010-03-16 6:01 ` Joanna Rutkowska
2010-03-17 13:35 ` Tobias Geiger
2010-03-17 15:21 ` Joanna Rutkowska
2010-03-17 16:20 ` Jeremy Fitzhardinge
2010-03-17 17:05 ` Joanna Rutkowska
2010-03-17 17:21 ` Jeremy Fitzhardinge
2010-03-17 16:26 ` Dan Magenheimer
2010-03-12 22:56 ` Tobias Geiger
2010-03-11 7:47 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2010-03-12 11:42 Tobias Geiger
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=4B96DB69.10101@goop.org \
--to=jeremy@goop.org \
--cc=joanna@invisiblethingslab.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).