On Mon, Feb 20, 2017 at 01:48:32PM +0000, Suzuki K Poulose wrote: > On 20/02/17 12:30, Mark Rutland wrote: > >The patch makes KVM handle any unknown EC by injecting an UNDEFINED > >exception into the guest, with a corresponding (ratelimited) warning in > >the host dmesg. We could later improve on this with with a new (opt-in) > >exit to the host userspace. > > If the unknown EC happens to be an asynchronous exception (allocated > from the second range), we are not sure if that was triggered by this > guest, or a different guest or even the hypervisor if we cannot really > isolate the exception(with/without the RAS extensions, i.e ESB). Sure; that is certainly a worry. > And I accept there may not be a perfect solution to the problem > either. May be we could explicitly mention about "unsure" exceptions, > so that it might help, people who may not really have the deep > knowledge about the exception code schemes. I guess we could, though I'm not sure how this is going to be helpful for those without an understanding of the EC values. We can only say it *may* be an asynchronous exception, so to understand the issue you need to understand the EC value. Thanks, Mark. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
