[Top][All Lists]

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

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

From: Sam Bobroff
Subject: Re: [Qemu-ppc] [PATCH v3 0/5] target-ppc/spapr: Add FWNMI support in QEMU for PowerKVM guests
Date: Thu, 17 Aug 2017 13:35:54 +1000
User-agent: NeoMutt/20170113 (1.7.2)

On Wed, Aug 16, 2017 at 02:41:59PM +0530, Aravinda Prasad wrote:
> This series of patches adds support for FWNMI in PowerKVM guests.
> Memory error such as bit flips 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 exception, if the address in error belongs
> to guest then KVM causes a guest exit with KVM_EXIT_NMI
> exit reason.
> This patch series adds functionality to pass on such
> machine check exception to the guest kernel by suitably
> handling KVM_EXIT_NMI exit and building the error log.
> The KVM changes are now part of the upstream kernel
> (commit e20bbd3d). This series contain QEMU changes.



I'm concerned that this implementation may introduce a problem with
kexec. If a VM registers an NMI handler, then kexecs to a new kernel
and an NMI is received before the new kernel has registered it's
handler, won't QEMU cause the guest to jump to the old, now invalid,
handler address? Is this worth worrying about?


reply via email to

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