Re: [Xen-devel] no definition of virtualization exception in exception table

[Big Strong]

Got it. Thanks for the replying.

2016-04-28 17:03 GMT+08:00 Andrew Cooper :

> On 28/04/16 09:53, George Dunlap wrote:
> > On Thu, Apr 28, 2016 at 3:37 AM, Big Strong  wrote:
> >> There is a #VE exception defined in p2086 of Intel Software Development
> >> Manual, however, no definition of exception handler is availble in Xen
> 4.6.
> >> Should I define the handler by myself by modifying the source code of
> xen,
> >> or is there a way to define the handler of the reserved IDT vectors
> (0-31,
> >> #VE is 20) without modifying the source code?
> > What are you actually trying to do?
> >
> > Xen shouldn't be generating #VEs itself, so it doesn't need a #VE
> > handler.  Those should only be generated by guests in HVM mode (if I'm
> > remembering things correctly).  In those cases the #VE will either be
> > delivered directly to the guest, or it will cause a VMEXIT.
>
> Correct.  #VE occurs from a EPT permission violation when appropriate
> controls are set up, and are either become a VMEXIT or an in-guest #VE
> depending on the .surpress_ve bit in a leaf epte.
>
> Unless you are nesting Xen inside another hypervisor on Intel hardware,
> and have opted in to receiving #VE's, you won't encounter any.
>
> ~Andrew
>
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] no definition of virtualization exception in exception table

[Andrew Cooper]

On 28/04/16 09:53, George Dunlap wrote:
> On Thu, Apr 28, 2016 at 3:37 AM, Big Strong  wrote:
>> There is a #VE exception defined in p2086 of Intel Software Development
>> Manual, however, no definition of exception handler is availble in Xen 4.6.
>> Should I define the handler by myself by modifying the source code of xen,
>> or is there a way to define the handler of the reserved IDT vectors (0-31,
>> #VE is 20) without modifying the source code?
> What are you actually trying to do?
>
> Xen shouldn't be generating #VEs itself, so it doesn't need a #VE
> handler.  Those should only be generated by guests in HVM mode (if I'm
> remembering things correctly).  In those cases the #VE will either be
> delivered directly to the guest, or it will cause a VMEXIT.

Correct.  #VE occurs from a EPT permission violation when appropriate
controls are set up, and are either become a VMEXIT or an in-guest #VE
depending on the .surpress_ve bit in a leaf epte.

Unless you are nesting Xen inside another hypervisor on Intel hardware,
and have opted in to receiving #VE's, you won't encounter any.

~Andrew

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

Re: [Xen-devel] no definition of virtualization exception in exception table

[George Dunlap]

On Thu, Apr 28, 2016 at 3:37 AM, Big Strong  wrote:
> There is a #VE exception defined in p2086 of Intel Software Development
> Manual, however, no definition of exception handler is availble in Xen 4.6.
> Should I define the handler by myself by modifying the source code of xen,
> or is there a way to define the handler of the reserved IDT vectors (0-31,
> #VE is 20) without modifying the source code?

What are you actually trying to do?

Xen shouldn't be generating #VEs itself, so it doesn't need a #VE
handler.  Those should only be generated by guests in HVM mode (if I'm
remembering things correctly).  In those cases the #VE will either be
delivered directly to the guest, or it will cause a VMEXIT.

 -George

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

[Xen-devel] no definition of virtualization exception in exception table

[Big Strong]

There is a #VE exception defined in p2086 of Intel Software Development
Manual, however, no definition of exception handler is availble in Xen 4.6.
Should
I define the handler by myself by modifying the source code of xen, or is
there a way to define the handler of the reserved IDT vectors (0-31, #VE is
20) without modifying the source code?
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel