From: Avi Kivity <avi@redhat.com>
To: "Nadav Har'El" <nyh@math.technion.ac.il>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: Why exit on MSR_STAR and friends?
Date: Thu, 17 Feb 2011 12:39:26 +0200 [thread overview]
Message-ID: <4D5CFADE.3050108@redhat.com> (raw)
In-Reply-To: <20110217102935.GA19369@fermat.math.technion.ac.il>
On 02/17/2011 12:29 PM, Nadav Har'El wrote:
> I guess I should be more worried why I got all these PIOs in L2 in the
> first place - the MSR reads and writes in L1 were just an odd consequence
> of that. It turns out that the "ping -f" workload I was running in L2
> insisted to get accurate timings of each packet, and this, I'm not still
> sure why, caused a ACPI PM_TIMER PIO for each packet. I guess that normal
> workloads won't use the timer on every packet, so that shouldn't matter.
Strange, isn't kvmclock exposed to L2?
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2011-02-17 10:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 15:17 Why exit on MSR_STAR and friends? Nadav Har'El
2011-02-17 9:22 ` Avi Kivity
2011-02-17 10:29 ` Nadav Har'El
2011-02-17 10:39 ` Avi Kivity [this message]
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=4D5CFADE.3050108@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nyh@math.technion.ac.il \
/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