Re: [Xen-devel] [PATCH 15/15] x86/hvm: Use system-segment relative memory accesses

2016-11-24 Thread Andrew Cooper
On 24/11/16 16:01, Jan Beulich wrote: On 23.11.16 at 16:38, wrote: >> --- a/xen/arch/x86/x86_emulate/x86_emulate.c >> +++ b/xen/arch/x86/x86_emulate/x86_emulate.c >> @@ -1181,20 +1181,38 @@ static int ioport_access_check( >> return rc; >> >> /* Ensure the TSS has an io-bitmap-

Re: [Xen-devel] [PATCH 15/15] x86/hvm: Use system-segment relative memory accesses

2016-11-24 Thread Jan Beulich
>>> On 23.11.16 at 16:38, wrote: > --- a/xen/arch/x86/x86_emulate/x86_emulate.c > +++ b/xen/arch/x86/x86_emulate/x86_emulate.c > @@ -1181,20 +1181,38 @@ static int ioport_access_check( > return rc; > > /* Ensure the TSS has an io-bitmap-offset field. */ > -generate_exception_if

[Xen-devel] [PATCH 15/15] x86/hvm: Use system-segment relative memory accesses

2016-11-23 Thread Andrew Cooper
With hvm_virtual_to_linear_addr() capable of doing proper system-segment relative memory accesses, avoid open-coding the address and limit calculations locally. When a table spans the 4GB boundary (32bit) or non-canonical boundary (64bit), segmentation errors are now raised. Previously, the use o