All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <george.dunlap@citrix.com>,
	Big Strong <fangtuo90@gmail.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: no definition of virtualization exception in exception table
Date: Thu, 28 Apr 2016 10:03:31 +0100	[thread overview]
Message-ID: <5721D1E3.2080603@citrix.com> (raw)
In-Reply-To: <CAFLBxZaG2PbNDKWa9YmRu-cHMg=vXEESsUv4A8u=1Fbi9gcEYg@mail.gmail.com>

On 28/04/16 09:53, George Dunlap wrote:
> On Thu, Apr 28, 2016 at 3:37 AM, Big Strong <fangtuo90@gmail.com> 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

  reply	other threads:[~2016-04-28  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  2:37 no definition of virtualization exception in exception table Big Strong
2016-04-28  8:53 ` George Dunlap
2016-04-28  9:03   ` Andrew Cooper [this message]
2016-04-28 10:45     ` Big Strong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5721D1E3.2080603@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=fangtuo90@gmail.com \
    --cc=george.dunlap@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.