Re: [Xen-devel] [V9 PATCH 7/8] pvh dom0: check for vioapic null ptr in vioapic_range

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 08.05.14 at 01:52, <mukesh.rathor@xxxxxxxxxx> wrote:
> What I am trying to tell is that I don't see #VE support in linux right
> now. Upstreaming that in my experience could be anywhere from 2 months
> to year depending on maintainers! Meanwhile, xen will crash if a pvh 
> guest causes ept violation.

That last aspect needs addressing, no question. But PVH is
experimental anyway, so fixing it by breaking upstream Linux is
_not_ a problem (and remember that I had always pointed out that
Linux support should be upstreamed only once the hypervisor
interface is completely understood, defined, and sufficiently
implemented, or the functionality should be called/marked
experimental [and hence subject to incompatible changes] there
too). I.e. injecting #VE into guests can very well be the solution to
the problem - for one, guests can avoid these exceptions from being
raised by not touching non-existent memory, and second it's clearly
better for guests than for the host to crash.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel