From: "Jan Beulich" <JBeulich@novell.com>
To: Jed Smith <jed@linode.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Runaway real/sys time in newer paravirt domUs?
Date: Fri, 09 Jul 2010 17:00:13 +0100 [thread overview]
Message-ID: <4C3763AD020000780000A8B1@vpn.id2.novell.com> (raw)
In-Reply-To: <E2930D8D-5FD1-4C1C-AFEA-C9EB9192AD2C@linode.com>
>>> 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.
Jan
next prev parent reply other threads:[~2010-07-09 16:00 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 [this message]
2010-07-13 21:10 ` Jed Smith
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=4C3763AD020000780000A8B1@vpn.id2.novell.com \
--to=jbeulich@novell.com \
--cc=jed@linode.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).