qemu-ppc
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-ppc] [PATCH v6 0/6] target-ppc/spapr: Add FWNMI support in QEM


From: David Gibson
Subject: Re: [Qemu-ppc] [PATCH v6 0/6] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests
Date: Wed, 13 Mar 2019 10:21:58 +1100
User-agent: Mutt/1.11.3 (2019-02-01)

On Tue, Mar 12, 2019 at 03:26:27PM +0100, Greg Kurz wrote:
> On Tue, 12 Mar 2019 15:32:51 +0530
> Aravinda Prasad <address@hidden> 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.
> > 
> 
> Hi Aravinda,
> 
> Please rebase this series because of the "spapr: Use CamelCase properly"
> patch, now merged in master:
> 
> https://git.qemu.org/?p=qemu.git;a=commit;h=ce2918cbc31e190e7d644c684dcc2bbcb6b9a9df

Indeed.  Unfortunately this isn't great timing for ths series: we've
just had the soft freeze, so this won't be able to go in until the 4.1
tree opens.

-- 
David Gibson                    | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au  | minimalist, thank you.  NOT _the_ _other_
                                | _way_ _around_!
http://www.ozlabs.org/~dgibson

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]