From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Dan Magenheimer <dan.magenheimer@oracle.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: rdtsc strangeness on upstream kernel
Date: Mon, 19 Jul 2010 16:34:59 -0700 [thread overview]
Message-ID: <4C44E123.3030308@goop.org> (raw)
In-Reply-To: <0784c7e7-1e9c-4abd-8e90-837051fe6b8b@default>
On 07/19/2010 04:19 PM, Dan Magenheimer wrote:
> In trying to understand some strange behavior I was
> seeing on a RHEL6b2 guest, I ran across an interesting
> anomaly, and it seems to be true on different upstream
> (pvops) kernels. At first I thought it was a result
> of the xen_sched_clock->xen_clocksource_read patch
> you recently posted, but after some testing this
> appears to be unrelated.
>
> The number of rdtsc/second goes up dramatically when
> there is CPU-intensive load on an upstream kernel!
>
Are you looking at rdtsc emulation traps when running a PV domain?
> I know we both observed some cases where rdtsc/sec
> was very high, but I don't think we ever were able to
> reproduce this consistently.
>
It would be interesting to compare that to the context switch rate (cs
column in vmstat output) to see if they correlate.
Also, how does it relate to timer interrupts?
> First, this is a single vcpu, 64-bit 2.6.32 (RHEL6b2)
> kernel.
>
> I am observing ~300 rdtsc/sec on an idle VM. When
> I run a load of:
>
> main() {while(1);}
>
> I am observing about 10000 rdtsc/sec!!
>
> This is a CONFIG_HZ_1000=y kernel, so I would
> expect 1000 rdtsc/sec, or maybe 2000 rdtsc/sec,
> but 10000 makes me wonder if there is some hidden
> bug.
>
Do you have preemption running? And why HZ=1000?
Thanks,
J
next prev parent reply other threads:[~2010-07-19 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 23:19 rdtsc strangeness on upstream kernel Dan Magenheimer
2010-07-19 23:34 ` Jeremy Fitzhardinge [this message]
2010-07-19 23:51 ` Dan Magenheimer
[not found] ` <681683ff-677b-4709-911e-3d90d7dbed7c@default4C44EF08.3070103@goop.org>
2010-07-19 23:55 ` Dan Magenheimer
2010-07-20 0:34 ` Jeremy Fitzhardinge
2010-07-20 0:42 ` Dan Magenheimer
2010-07-20 0:44 ` Jeremy Fitzhardinge
2010-07-23 16:47 ` Dan Magenheimer
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=4C44E123.3030308@goop.org \
--to=jeremy@goop.org \
--cc=dan.magenheimer@oracle.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.