From: Sheng Yang <sheng@linux.intel.com>
To: Avi Kivity <avi@redhat.com>
Cc: Joerg Roedel <joro@8bytes.org>,
"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>,
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: Tue, 20 Apr 2010 11:32:55 +0800 [thread overview]
Message-ID: <201004201132.56039.sheng@linux.intel.com> (raw)
In-Reply-To: <4BCC136D.503@redhat.com>
On Monday 19 April 2010 16:25:17 Avi Kivity wrote:
> On 04/17/2010 09:12 PM, Avi Kivity wrote:
> > I think you were right the first time around.
>
> Re-reading again (esp. the part about treatment of indirect NMI
> vmexits), I think this was wrong, and that the code is correct. I am
> now thoroughly confused.
>
My fault...
To my understanding now, "If an event causes a VM exit directly, it does not
update architectural state as it would have if it had it not caused the VM
exit:", means: in NMI case, NMI would involve the NMI handler, and change the
"architectural state" to NMI block. In VMX non-root mode, the behavior of
calling NMI handler changed(determine by some VMCS fields), but not the
affection to the "architectural state". So the NMI block state would remain
the same.
--
regards
Yang, Sheng
next prev parent reply other threads:[~2010-04-20 3:33 UTC|newest]
Thread overview: 34+ 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
2030-04-14 9:05 ` 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
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
2030-04-15 1:04 ` Zhang, Yanmin
2010-04-15 8:05 ` Avi Kivity
2010-04-15 8:58 ` Zhang, Yanmin
2030-04-15 8:57 ` 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-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 [this message]
2010-04-20 9:38 ` Avi Kivity
2010-04-27 19:03 ` [PATCH] Psychovisually-optimized HZ setting (2.6.33.3) Uwaysi Bin Kareem
2010-04-27 19:51 ` Randy Dunlap
2010-04-27 21:50 ` Valdis.Kletnieks
2010-04-15 8:58 ` [PATCH V3] perf & kvm: Enhance perf to collect KVM guest os statistics from host side 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=201004201132.56039.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 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.