From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
Subject: Re: VMX check_for_null_selector()
Date: Wed, 22 Nov 2006 09:47:37 +0000 [thread overview]
Message-ID: <C189CD39.4DD3%keir@xensource.com> (raw)
In-Reply-To: <45641C8F.76E4.0078.0@novell.com>
Good question, it's something I've been meaning to ask the Intel guys
about...
K.
On 22/11/06 08:46, "Jan Beulich" <jbeulich@novell.com> wrote:
> What is the hidden background for using this function when the guest
> is in protected mode? When the selector used is a null one (and not
> in 64-bit mode), the instruction should not cause an
> EXIT_REASON_IO_INSTRUCTION exit at all, but rather should cause
> a GP fault in the guest. In 64-bit mode, a null selector isn't invalid,
> and hence doesn't need checking for.
> What I'm trying to determine is whether the function must be fixed
> (to deal with (a) non-zero CS base addresses and (b) the fact that
> on INS there shouldn't be checking for segment overrides, but ES
> should be used in all cases) or can be removed.
>
> Thanks, Jan
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2006-11-22 9:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 8:46 VMX check_for_null_selector() Jan Beulich
2006-11-22 9:47 ` Keir Fraser [this message]
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=C189CD39.4DD3%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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.