From: Sheng Yang <sheng@linux.intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
oerg Roedel <joro@8bytes.org>,
Jes Sorensen <Jes.Sorensen@redhat.com>,
Gleb Natapov <gleb@redhat.com>,
Zachary Amsden <zamsden@redhat.com>,
zhiteng.huang@intel.com, tim.c.chen@intel.com,
Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: Re: [PATCH V3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side
Date: Wed, 14 Apr 2010 18:14:19 +0800 [thread overview]
Message-ID: <201004141814.19330.sheng@linux.intel.com> (raw)
In-Reply-To: <4BC5919E.1010400@redhat.com>
On Wednesday 14 April 2010 17:57:50 Avi Kivity wrote:
> On 04/14/2010 12:43 PM, Sheng Yang wrote:
> > On Wednesday 14 April 2010 17:20:15 Avi Kivity wrote:
> >> On 04/14/2030 12:05 PM, Zhang, Yanmin wrote:
> >>> Here is the new patch of V3 against tip/master of April 13th
> >>> if anyone wants to try it.
> >>
> >> Thanks for persisting despite the flames.
> >>
> >> Can you please separate arch/x86/kvm part of the patch? That will make
> >> for easier reviewing, and will need to go through separate trees.
> >>
> >> Sheng, did you make any progress with the NMI injection issue?
> >
> > Yes, though some other works interrupt me lately...
> >
> > The very first version has issue due to SELF_IPI mode can't be used to
> > send NMI according to SDM. That's the reason why x2apic don't have way to
> > do this.
>
> Yes, I see that now. Looks like others have the same questions...
>
> > But later I found another issue of fail to inspect inside the guest. I
> > think it's due to NMI is asynchronous event, though it should be
> > triggered very quickly, you can't guarantee that the handler would be
> > triggered before the state(current_vcpu) is cleared with current code.
> >
> > Maybe just extended the "guest state" region would be fine, if the
> > latency is stable enough(though I think it maybe platform depended). I am
> > working on this now.
>
> I wouldn't like to depend on model specific behaviour.
>
> One option is to read all the information synchronously and store it in
> a per-cpu area with atomic instructions, then queue the NMI. Another
> option is to have another callback which tells us that the NMI is done,
> and have a busy loop wait until the NMI is delivered.
>
Callback seems too heavy, may affect the performance badly. Maybe a short
queue would help, though this one is more complex.
But I am still curious if we extend the region, how much it would help. Would
get a result soon...
--
regards
Yang, Sheng
next prev parent reply other threads:[~2010-04-14 10:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 9:06 [PATCH V3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side Zhang, Yanmin
2010-04-14 9:20 ` Avi Kivity
2010-04-14 9:43 ` Sheng Yang
2010-04-14 9:57 ` Avi Kivity
2010-04-14 10:14 ` Sheng Yang [this message]
2010-04-14 10:19 ` Avi Kivity
2010-04-14 10:27 ` Sheng Yang
2010-04-14 10:33 ` Avi Kivity
2010-04-14 10:36 ` Sheng Yang
2010-04-14 10:43 ` Ingo Molnar
2010-04-14 11:17 ` Avi Kivity
2010-04-15 1:05 ` Zhang, Yanmin
2010-04-15 8:05 ` Avi Kivity
2010-04-15 8:58 ` Zhang, Yanmin
2010-04-15 9:04 ` oerg Roedel
2010-04-15 9:09 ` Avi Kivity
2010-04-15 9:44 ` oerg Roedel
2010-04-15 9:48 ` Avi Kivity
2010-04-15 10:40 ` Joerg Roedel
2010-04-15 10:44 ` Avi Kivity
2010-04-15 14:08 ` Sheng Yang
2010-04-17 18:12 ` Avi Kivity
2010-04-19 8:25 ` Avi Kivity
2010-04-20 3:32 ` Sheng Yang
2010-04-20 9:38 ` Avi Kivity
2010-04-15 8:58 ` Zhang, Yanmin
2010-04-15 1:05 ` Zhang, Yanmin
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=201004141814.19330.sheng@linux.intel.com \
--to=sheng@linux.intel.com \
--cc=Jes.Sorensen@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=tim.c.chen@intel.com \
--cc=yanmin_zhang@linux.intel.com \
--cc=zamsden@redhat.com \
--cc=zhiteng.huang@intel.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