From: Andi Kleen <andi@firstfloor.org>
To: Avi Kivity <avi@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>,
ying.huang@intel.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2/2] KVM: Add VT-x machine check support
Date: Thu, 4 Jun 2009 15:01:07 +0200 [thread overview]
Message-ID: <20090604130107.GA1065@one.firstfloor.org> (raw)
In-Reply-To: <4A27C2BF.3090108@redhat.com>
On Thu, Jun 04, 2009 at 03:49:03PM +0300, Avi Kivity wrote:
> Andi Kleen wrote:
> >>This assumption is incorrect. This code is executed after preemption
> >>has been enabled, and we may have even slept before reaching it.
> >>
> >
> >The only thing that counts here is the context before the machine
> >check event. If there was a vmexit we know it was in guest context.
> >
> >The only requirement we have is that we're running still on the same
> >CPU. I assume that's true, otherwise the vmcb accesses wouldn't work?
> >
>
> It's not true, we're in preemptible context and may have even slept.
>
> vmcs access work because we have a preempt notifier called when we are
> scheduled in, and will execute vmclear/vmptrld as necessary. Look at
> kvm_preempt_ops in virt/kvm_main.c.
I see. So we need to move that check earlier. Do you have a preference
where it should be?
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-06-04 12:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 11:12 [PATCH] [1/2] x86: MCE: Define MCE_VECTOR Andi Kleen
2009-06-04 11:12 ` [PATCH] [2/2] KVM: Add VT-x machine check support Andi Kleen
2009-06-04 11:48 ` Avi Kivity
2009-06-04 12:51 ` Andi Kleen
2009-06-04 12:49 ` Avi Kivity
2009-06-04 13:01 ` Andi Kleen [this message]
2009-06-04 13:10 ` Avi Kivity
2009-06-04 13:20 ` Andi Kleen
2009-06-04 13:49 ` Avi Kivity
2009-06-04 14:07 ` Andi Kleen
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=20090604130107.GA1065@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.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.