Hi James, On 2017/10/17 0:59, James Morse wrote: >>> Do we really care about old guests in this case? > I think the scenario here is the host kernel has some RAS support, Qemu has > RAS > support and has advertised its CPER regions via the HEST, but the guest > doesn't > doesn't support RAS. (booted via DT, wasn't configured for APEI, the kernel > pre-dates the support etc). > > What should Qemu do in response to 'action optional' memory errors? > > My suggestion is whatever action Qemu takes, it shouldn't kill a guest that > doesn't support RAS. Using NOTIFY_SEI for an action-optional memory error will > do this. A guest that doesn't know about NOTIFY_SEI will take this as a fatal > SError.
In short, if for this purpose, I think NOTIFY_GPIO meets the requirement, which will not kill a guest which does not support RAS, and keep the ACPI the spec, so I suggestion using NOTIFY_GPIO to 'action optional' memory errors > >
