RE: [Xen-devel] trap/interrupt gate for hypercall

["Jan Beulich" <jbeulich@xxxxxxxxxx>]

>Enter Xen on hypercall, immediately take an interrupt, on return from
>interrupt %es faults on reload. How do we propagate this bad segment
>   --> the problem is when return from interrupt how %es faults on reload
>       except interrupt handler purposely modify kernel stack? --> example?

By the guest modifying the referenced descriptor from another vCPU.

>register value to the guest via the failsafe callback handler from this
>context? The bad %es is not yet saved on the outer context's stack frame.

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel