linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: KVM <kvm@vger.kernel.org>, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Joerg Roedel" <joro@8bytes.org>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Tony Luck" <tony.luck@intel.com>,
	"Yazen Ghannam" <Yazen.Ghannam@amd.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/2] x86/kvm: Enable MCE injection in the guest
Date: Sun, 13 Jan 2019 15:37:19 +0100	[thread overview]
Message-ID: <20190113143719.GA25673@zn.tnic> (raw)
In-Reply-To: <64d0e75f-f292-7e63-dd66-4e05d4afed5b@redhat.com>

On Mon, Nov 26, 2018 at 05:41:21PM +0100, Paolo Bonzini wrote:
> On 14/11/18 19:15, Borislav Petkov wrote:
> > From: Borislav Petkov <bp@suse.de>
> > 
> > Hi all,
> > 
> > here's a rediff ontop of -rc2. No changes, only added Yazen's Tested-by.
> > 
> > Please queue,
> > thx.
> > 
> > Changelog:
> > ==========
> > 
> > v2:
> > 
> > here's v2, dropping patch 3 and incorporating hopefully all of Radim's
> > feedback.
> > 
> > v1:
> > 
> > there's this mce-inject.ko module in the kernel which allows for
> > injecting real MCEs and thus test the MCE handling code.
> > 
> > It is doubly useful to be able to inject same MCEs in a guest so that
> > testing of the MCE handling code can happen even easier/faster. In order
> > to be able to do that on an AMD guest, we need to emulate some bits
> > and pieces like the HWCR[McStatusWrEn] bit which allows writes to the
> > MCi_STATUS registers without a #GP.
> > 
> > The below does that and with it I'm able to properly inject MCEs in said
> > guest.
> > 
> > --
> > 
> > Borislav Petkov (2):
> >   kvm/x86: Move MSR_K7_HWCR to svm.c
> >   x86/kvm: Implement MSR_HWCR support
> > 
> >  arch/x86/kvm/svm.c | 20 ++++++++++++++++++++
> >  arch/x86/kvm/x86.c | 46 +++++++++++++++++++++++++++++++---------------
> >  2 files changed, 51 insertions(+), 15 deletions(-)
> > 
> 
> Queued, thanks.

Where?

I don't see them in rc1...

-- 
Regards/Gruss,
    Boris.

Good mailing practices for 400: avoid top-posting and trim the reply.

      reply	other threads:[~2019-01-13 14:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-14 18:15 [PATCH v3 0/2] x86/kvm: Enable MCE injection in the guest Borislav Petkov
2018-11-14 18:15 ` [PATCH v3 1/2] kvm/x86: Move MSR_K7_HWCR to svm.c Borislav Petkov
2018-11-26 15:33   ` David Hildenbrand
2018-11-14 18:15 ` [PATCH v3 2/2] x86/kvm: Implement MSR_HWCR support Borislav Petkov
2018-11-26 16:41 ` [PATCH v3 0/2] x86/kvm: Enable MCE injection in the guest Paolo Bonzini
2019-01-13 14:37   ` Borislav Petkov [this message]

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=20190113143719.GA25673@zn.tnic \
    --to=bp@alien8.de \
    --cc=Yazen.Ghannam@amd.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=thomas.lendacky@amd.com \
    --cc=tony.luck@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;
as well as URLs for NNTP newsgroup(s).