On Tue, Feb 04, 2020 at 03:47:15PM +0100, Vitaly Kuznetsov wrote: > Sean Christopherson <sean.j.christopherson@xxxxxxxxx> writes: > > > Exiting to host userspace with "emulation failed" is the other reasonable > > alternative, but that's basically the same as killing the guest. We're > > arguing that, in the extremely unlikely event that there is a workload out > > there that hits this, it's preferable to *maybe* corrupt guest memory and > > log the anomaly in the kernel log, as opposed to outright killing the guest > > with a generic "emulation failed". > > > > FWIW, if I was to cast a vote I'd pick 'kill the guest' one way or > another. "Maybe corrupt guest memory" scares me much more and in many > cases host and guest are different responsibility domains (think > 'cloud'). I'm ok with that route as well. What I don't want to do is add a bunch of logic to inject #AC at this point.
