Re: [Xen-devel] [V10 PATCH 09/23] PVH xen: introduce pvh_set_vcpu_info() and vmx_pvh_set_vcpu_info()

[Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>]

On Mon, 12 Aug 2013 14:24:32 +0100
"Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> >>> On 12.08.13 at 13:53, Tim Deegan <tim@xxxxxxx> wrote:
> > At 12:04 +0100 on 12 Aug (1376309065), Jan Beulich wrote:
> >> >>> On 12.08.13 at 12:24, Tim Deegan <tim@xxxxxxx> wrote:
> >> > At 08:54 +0100 on 12 Aug (1376297674), Jan Beulich wrote:
> >> >> >>> On 10.08.13 at 01:41, Mukesh Rathor
........
> > 
> > Ah, you're right, that's explicilty disallowed. :(  Xen could set
> > any non-null descriptor (still requiring the caller to specify null
> > descriptors and documenting that the descriptor registers will be
> > undefined until the guest loads them on the new vcpu).
> 
> Hmm, yes, I don't really like starting a guest with inconsistent
> state, but it's an option.
> 
> > If we really require the selectors to match the GDT contents then we
> > either have to constrain the selector/GDT contents (a horrible
> > interface) or properly emulate the loads (which surely we already
> > have code in Xen to do).
> 
> protmode_load_seg() in the x86 emulation code appears to be the
> only one. But it doesn't seem impossible to leverage this here.

hvm_load_segment_selector() will do it.

Mukesh

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