From: Jed Smith <jed@linode.com>
To: Jan Beulich <JBeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Runaway real/sys time in newer paravirt domUs?
Date: Tue, 13 Jul 2010 17:10:04 -0400 [thread overview]
Message-ID: <2EAEA978-EFA7-4B97-A414-48A98479D845@linode.com> (raw)
In-Reply-To: <4C3763AD020000780000A8B1@vpn.id2.novell.com>
On Jul 9, 2010, at 12:00 PM, Jan Beulich wrote:
>>>> On 09.07.10 at 16:57, Jed Smith <jed@linode.com> wrote:
>> On Jul 9, 2010, at 4:46 AM, Jan Beulich wrote:
>>> Is this perhaps also dependent on the CPU make/model?
>> - Between 2.6.29 and 2.6.30, /proc/uptime behaves much differently, and the
>> bug
>> then exposes itself. Something changed there.
>
> Others as well as me had seen similar misbehavior (outside of pv-ops),
> but only on reasonably new Intel systems. sched_clock_stable getting
> set to one in arch/x86/kernel/cpu/intel.c turned out to be the problem.
Is there a way to test this that I could perform for you? We're getting
more reports of the same issue in our newer kernels. Do you think
CONFIG_NO_HZ makes a difference either way?
Regards,
Jed Smith
Systems Administrator
Linode, LLC
+1 (609) 593-7103 x1209
jed@linode.com
next prev parent reply other threads:[~2010-07-13 21:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 16:32 Runaway real/sys time in newer paravirt domUs? Jed Smith
2010-07-06 19:05 ` Jeremy Fitzhardinge
2010-07-06 20:20 ` Jed Smith
2010-07-08 16:38 ` Jed Smith
2010-07-09 8:46 ` Jan Beulich
2010-07-09 14:57 ` Jed Smith
2010-07-09 16:00 ` Jan Beulich
2010-07-13 21:10 ` Jed Smith [this message]
2010-07-14 16:31 ` Jed Smith
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=2EAEA978-EFA7-4B97-A414-48A98479D845@linode.com \
--to=jed@linode.com \
--cc=JBeulich@novell.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 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.