On 03/10/2010 12:36 AM, Jeremy Fitzhardinge wrote:
> 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-184.108.40.206-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
> What is the hardware platform?
Intel Core 2 Duo, Intel PM45 chipset.
> How many CPUs are you using?
2 cores, all CPU-specific power management in BIOS disabled.
> Does pinning the vcpus to pcpus help?
xm vcpu-pin <dom> all all
for all my running domains, and it didn't change anything.
But not sure if this is correct? Perhaps I should do:
xm vcpu-pin <dom> 0 0
xm vcpu-pin <dom> 1 1
Perhaps there is a boot option to do the same system-wide?
>> 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.
Interestingly, this keyboard hiccup effect does not occur in DomUs, only
in Dom0. However, the DomUs clearly experience some scheduling problems
-- e.g. sometime programs take a loooong time to start up, just like if
their CPU time was miscalculated and they were constantly preempted, but
xentop doesn't show any high load anywhere.
Occasionally this is visible in both Dom0's and DomU's dmesgs:
Clocksource tsc unstable (delta = 62752834 ns)
hrtimer: interrupt too slow, forcing clock min delta to 412700358 ns
> I don't remember if 3.4.2 ended up with tsc emulation, but if it does
> you might try enabling it.
TSC emulation? But I'm running only PV guests. Not sure what do you mean
by this, or how to enable it?
Description: OpenPGP digital signature
Xen-devel mailing list