From: Greg Kurz <groug@kaod.org>
To: Aravinda Prasad <aravinda@linux.vnet.ibm.com>
Cc: aik@au1.ibm.com, qemu-devel@nongnu.org, paulus@ozlabs.org,
qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [Qemu-ppc] [patch-for-4.2 PATCH v11 0/6] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests
Date: Thu, 29 Aug 2019 12:55:30 +0200 [thread overview]
Message-ID: <20190829125530.7f79efc1@bahia.lan> (raw)
In-Reply-To: <35775479-e5fe-fc90-cc19-d6b6f8f3a570@linux.vnet.ibm.com>
On Thu, 29 Aug 2019 16:08:53 +0530
Aravinda Prasad <aravinda@linux.vnet.ibm.com> wrote:
>
>
> On Thursday 29 August 2019 03:51 PM, Greg Kurz wrote:
> > On Wed, 14 Aug 2019 11:40:50 +0530
> > Aravinda Prasad <aravinda@linux.vnet.ibm.com> wrote:
> >
> >> This patch set adds support for FWNMI in PowerKVM guests.
> >>
> >> System errors such as SLB multihit and memory errors
> >> that cannot be corrected by hardware is passed on to
> >> the kernel for handling by raising machine check
> >> exception (an NMI). Upon such machine check exceptions,
> >> if the address in error belongs to guest then KVM
> >> invokes guests' 0x200 interrupt vector if the guest
> >> is not FWNMI capable. For FWNMI capable guest
> >> KVM passes the control to QEMU by exiting the guest.
> >>
> >> This patch series adds functionality to QEMU to pass
> >> on such machine check exceptions to the FWNMI capable
> >> guest kernel by building an error log and invoking
> >> the guest registered machine check handling routine.
> >>
> >> The KVM changes are now part of the upstream kernel
> >> (commit e20bbd3d). This series contain QEMU changes.
> >>
> >> Change Log v11:
> >> - Moved FWNMI SPAPR cap defaults to 4.2 class option
> >> - Fixed issues with handling fwnmi KVM capability
> >>
> >
> > Hi Aravinda,
> >
> > I'm afraid this series needs rebasing. It doesn't apply
> > cleanly on current ppc-for-4.2 (SHA1 b1e8156743).
>
> This was based on the latest 4.2 at the time of posting (14th Aug).
I was on vacation at that time but you're probably right.
> Meanwhile may be due to changes to 4.2 it is not applying cleanly. I
> will rebase it to the latest 4.2 and post it again.
>
Thanks !
> Regards,
> Aravinda
>
> >
> > Cheers,
> >
> > --
> > Greg
> >
> >> Change Log v10:
> >> - Reshuffled the patch sequence + minor fixes
> >>
> >> Change Log v9:
> >> - Fixed kvm cap and spapr cap issues
> >>
> >> Change Log v8:
> >> - Added functionality to check FWNMI capability during
> >> VM migration
> >> ---
> >>
> >> Aravinda Prasad (6):
> >> Wrapper function to wait on condition for the main loop mutex
> >> ppc: spapr: Introduce FWNMI capability
> >> target/ppc: Handle NMI guest exit
> >> target/ppc: Build rtas error log upon an MCE
> >> ppc: spapr: Handle "ibm,nmi-register" and "ibm,nmi-interlock" RTAS calls
> >> migration: Include migration support for machine check handling
> >>
> >>
> >> cpus.c | 5 +
> >> hw/ppc/spapr.c | 78 +++++++++++++
> >> hw/ppc/spapr_caps.c | 29 +++++
> >> hw/ppc/spapr_events.c | 268 ++++++++++++++++++++++++++++++++++++++++++++++
> >> hw/ppc/spapr_rtas.c | 78 +++++++++++++
> >> include/hw/ppc/spapr.h | 25 ++++
> >> include/qemu/main-loop.h | 8 +
> >> target/ppc/cpu.h | 1
> >> target/ppc/kvm.c | 38 +++++++
> >> target/ppc/kvm_ppc.h | 13 ++
> >> target/ppc/trace-events | 1
> >> 11 files changed, 542 insertions(+), 2 deletions(-)
> >>
> >> --
> >> Signature
> >
> >
>
prev parent reply other threads:[~2019-08-29 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 6:10 [Qemu-devel] [patch-for-4.2 PATCH v11 0/6] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests Aravinda Prasad
2019-08-14 6:10 ` [Qemu-devel] [patch-for-4.2 PATCH v11 1/6] Wrapper function to wait on condition for the main loop mutex Aravinda Prasad
2019-08-14 6:11 ` [Qemu-devel] [patch-for-4.2 PATCH v11 2/6] ppc: spapr: Introduce FWNMI capability Aravinda Prasad
2019-08-14 6:11 ` [Qemu-devel] [patch-for-4.2 PATCH v11 3/6] target/ppc: Handle NMI guest exit Aravinda Prasad
2019-08-29 10:24 ` Greg Kurz
2019-08-14 6:11 ` [Qemu-devel] [patch-for-4.2 PATCH v11 4/6] target/ppc: Build rtas error log upon an MCE Aravinda Prasad
2019-08-14 6:11 ` [Qemu-devel] [patch-for-4.2 PATCH v11 5/6] ppc: spapr: Handle "ibm, nmi-register" and "ibm, nmi-interlock" RTAS calls Aravinda Prasad
2019-08-14 6:11 ` [Qemu-devel] [patch-for-4.2 PATCH v11 6/6] migration: Include migration support for machine check handling Aravinda Prasad
2019-08-29 10:21 ` [Qemu-devel] [patch-for-4.2 PATCH v11 0/6] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests Greg Kurz
2019-08-29 10:38 ` [Qemu-devel] [Qemu-ppc] " Aravinda Prasad
2019-08-29 10:55 ` Greg Kurz [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=20190829125530.7f79efc1@bahia.lan \
--to=groug@kaod.org \
--cc=aik@au1.ibm.com \
--cc=aravinda@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@ozlabs.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).