mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Avi Kivity <avi@redhat.com>
Cc: Andi Kleen <andi@firstfloor.org>, Andi Kleen <ak@linux.intel.com>,
	Stefan Lippers-Hollmann <s.L-H@gmx.de>,
	linux-kernel@vger.kernel.org, ying.huang@intel.com,
	stable@kernel.org
Subject: Re: patch kvm-add-vt-x-machine-check-support.patch added to 2.6.30-stable tree
Date: Wed, 1 Jul 2009 07:58:36 -0700	[thread overview]
Message-ID: <20090701145836.GA8480@suse.de> (raw)
In-Reply-To: <4A4B76F3.6070604@redhat.com>

On Wed, Jul 01, 2009 at 05:47:15PM +0300, Avi Kivity wrote:
> On 07/01/2009 05:18 PM, Andi Kleen wrote:
> > On Wed, Jul 01, 2009 at 04:41:54PM +0300, Avi Kivity wrote:
> >    
> >> Should be in struct vmx_vcpu; otherwise ack.
> >>      
> >
> > Done
> >
> > ---
> >
> > KVM: Add VT-x machine check support v4
> >
> > VT-x needs an explicit MC vector intercept to handle machine checks in the
> > hypervisor.
> >
> > It also has a special option to catch machine checks that happen
> > during VT entry.
> >
> > Do these interceptions and forward them to the Linux machine check
> > handler. Make it always look like user space is interrupted because
> > the machine check handler treats kernel/user space differently.
> >
> > Thanks to Huang Ying and Jiang Yunhong for help and testing.
> >
> >    
> 
> Ack, thanks.  Stable boys, please use this instead of the patch from 
> mainline and the two patches it dragged in.

So, I should use this instead of:
	kvm-vmx-fix-handling-of-a-fault-during-nmi-unblocked-due-to-iret.patch
	kvm-move-exit-due-to-nmi-handling-into-vmx_complete_interrupts.patch
	kvm-add-vt-x-machine-check-support.patch

thanks,

greg k-h

  reply	other threads:[~2009-07-01 14:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090629184144.76C9948FD3@coco.kroah.org>
2009-06-30 22:53 ` Stefan Lippers-Hollmann
2009-06-30 23:42   ` Greg KH
2009-07-01  7:09     ` Andi Kleen
2009-07-01  7:35       ` Avi Kivity
2009-07-01 13:24         ` Andi Kleen
2009-07-01 13:41           ` Avi Kivity
2009-07-01 14:18             ` Andi Kleen
2009-07-01 14:47               ` Avi Kivity
2009-07-01 14:58                 ` Greg KH [this message]
2009-07-01 15:04                   ` Avi Kivity
2009-07-01 17:27                     ` [stable] " Greg KH
2009-07-01 18:18                       ` Avi Kivity
2009-07-01 18:42                         ` Greg KH
2009-07-01 18:56                           ` Avi Kivity
2009-07-01 19:31                             ` Greg KH
2009-07-02 13:21                               ` Avi Kivity

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=20090701145836.GA8480@suse.de \
    --to=gregkh@suse.de \
    --cc=ak@linux.intel.com \
    --cc=andi@firstfloor.org \
    --cc=avi@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.L-H@gmx.de \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome