public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Roedel, Joerg" <Joerg.Roedel@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@kernel.org" <stable@kernel.org>
Subject: Re: [PATCH 1/2] KVM: SVM: Fix NMI path when NMI happens in guest mode
Date: Thu, 13 Jan 2011 16:51:29 +0100	[thread overview]
Message-ID: <20110113155129.GA23914@amd.com> (raw)
In-Reply-To: <4D2F1D49.8070807@redhat.com>

On Thu, Jan 13, 2011 at 10:42:01AM -0500, Avi Kivity wrote:
> On 01/13/2011 05:22 PM, Joerg Roedel wrote:
> > The vmexit path on SVM needs to restore the KERNEL_GS_BASE
> > MSR in order to savely execute the NMI handler. Otherwise a
> > pending NMI can occur after the STGI instruction and crash
> > the machine.
> > This makes it impossible to run perf and kvm in parallel on
> > an AMD machine in a stable way.
> >
> > Cc: stable@kernel.org
> > Signed-off-by: Joerg Roedel<joerg.roedel@amd.com>
> > ---
> >   arch/x86/kvm/svm.c |    1 +
> >   1 files changed, 1 insertions(+), 0 deletions(-)
> >
> > diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> > index 25bd1bc..8b9bc72 100644
> > --- a/arch/x86/kvm/svm.c
> > +++ b/arch/x86/kvm/svm.c
> > @@ -3637,6 +3637,7 @@ static void svm_vcpu_run(struct kvm_vcpu *vcpu)
> >
> >   #ifdef CONFIG_X86_64
> >   	wrmsrl(MSR_GS_BASE, svm->host.gs_base);
> > +	wrmsrl(MSR_KERNEL_GS_BASE, current->thread.gs);
> >   #else
> >   	loadsegment(fs, svm->host.fs);
> >   #endif
> 
> Why would an NMI crash if MSR_KERNEL_GS_BASE is bad?
> 
> I see save_paranoid depends on MSR_GS_BASE (specifically its sign, which 
> is bad for the new instructions that allow userspace to write gsbase), 
> but not on MSR_KERNEL_GS_BASE.

Thats a good question. I have not idea. I spent some time trying to
figure this out (after I found out that wrong KERNEL_GS_BASE was the
cause of the crashes) but had no luck.

This also doesn't happen every time an NMI is delivered in svm_vcpu_run.
Sometimes it runs perfectly in parallel for a few minutues before the
machine triple-faults.

I also had a look at entry_64.S. The save_paranoid could not be the
cause because MSR_GS_BASE is already negative at this point. But the
re-schedule condition check at the end of the NMI handler code could
also not be the cause because the NMI happens while preemption (and
interrupts) are disabled (a re-schedule should also trigger
preempt-notifiers and restore KERNEL_GS_BASE).

	Joerg

-- 
AMD Operating System Research Center

Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen, HRB Nr. 43632


  reply	other threads:[~2011-01-13 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 15:22 [PATCH 0/2] perf-kvm support for SVM Joerg Roedel
2011-01-13 15:22 ` [PATCH 1/2] KVM: SVM: Fix NMI path when NMI happens in guest mode Joerg Roedel
2011-01-13 15:42   ` Avi Kivity
2011-01-13 15:51     ` Roedel, Joerg [this message]
2011-01-13 19:27       ` Avi Kivity
2011-01-14 13:36         ` Roedel, Joerg
2011-01-13 15:48   ` Jan Kiszka
2011-01-13 15:52     ` Roedel, Joerg
2011-01-13 15:22 ` [PATCH 2/2] KVM: SVM: Add support for perf-kvm Joerg Roedel

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=20110113155129.GA23914@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=stable@kernel.org \
    /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