[PATCH] KVM: arm/arm64: Signal SIGBUS when stage2 discovers hwpoison memory
gengdj.1984 at gmail.com
Thu Apr 6 08:06:22 PDT 2017
thanks for the mail.
2017-04-06 17:25 GMT+08:00, James Morse <james.morse at arm.com>:
> Hi gengdongjiu,
> On 05/04/17 00:05, gengdongjiu wrote:
>> thanks for the patch, have you consider to told Qemu or KVM tools
>> the reason for this bus error(SEA/SEI)?
> They should never need to know. We should treat Qemu/kvmtool like any other
> program. Programs should only need to know about the affect on them, not
> underlying reason or mechanism.
>> when Qemu or KVM tools get this SIGBUS signal, it do not know receive
>> this SIGBUS due to SEA or SEI.
> Why would this matter?
> Firmware signalled Linux that something bad happened. Linux handles the
> and everything keeps running.
> The interface with firmware has to be architecture specific. When
> user-space it should be architecture agnostic, otherwise we can't write
> user space code.
> If Qemu was affected by the error (currently only if some of its memory was
> hwpoisoned) we send it SIGBUS as we would for any other program. Qemu can
> if and how to signal the guest about this error, it doesn't have to use the
> interface as firmware and the host used. With TCG Qemu may be emulating a
> totally different architecture!
> Looking at the list of errors in table 250 of UEFI 2.6, cache-errors are
> only case I can imagine we would want to report to a guest, these are
> effectively transient memory errors. SIGBUS is still appropriate here, but
> probably need a new si_code value to indicate the error can be cleared.
> hwpoison which appears to never re-use the affected page).
I understand your idea.
Below is my previous idea:
When signalling Qemu, Qemu generate GHES ,then Qemu/kvmtool inject
the SEA/SEI to guest OS. For different reason, Qemu/.KVMtool injects
diferent notification type. if inject SEA/SEI/IRQ, guest OS handle the
guest SEA/SEI/IRQ. handling guest OS SEA/SEI and IRQ guest OS software
logical is different.
for example, guest OS call API "ghes_notify_sea" when happening SEA;
call API "ghes_notify_sei" when happening SEI.
so what is your suggested way to notify guest OS after Qemu generating the CPER?
X86 Qemu uses below method(send acpi event) to notify guest OS for
runtime modification CPER, this method should not through KVM.
/* Send _GPE.E05 event */
so for the notification guest OS, I think Qemu uses IOCTL to let KVM
inject error may be better.
More information about the linux-arm-kernel