Re: [Xen-devel] [PATCH 01/11] VMX: VMFUNC and #VE definitions and detection.

2015-01-14 Thread Andrew Cooper
On 13/01/15 18:50, Ed White wrote: > On 01/12/2015 05:06 AM, Andrew Cooper wrote: >> On 09/01/15 21:26, Ed White wrote: >>> Currently, neither is enabled globally but may be enabled on a per-VCPU >>> basis by the altp2m code. >>> >>> Everything can be force-disabled globally by specifying vmfunc=0

Re: [Xen-devel] [PATCH 01/11] VMX: VMFUNC and #VE definitions and detection.

2015-01-13 Thread Ed White
On 01/12/2015 05:06 AM, Andrew Cooper wrote: > On 09/01/15 21:26, Ed White wrote: >> Currently, neither is enabled globally but may be enabled on a per-VCPU >> basis by the altp2m code. >> >> Everything can be force-disabled globally by specifying vmfunc=0 on the >> Xen command line. >> >> Remove t

Re: [Xen-devel] [PATCH 01/11] VMX: VMFUNC and #VE definitions and detection.

2015-01-12 Thread Andrew Cooper
On 09/01/15 21:26, Ed White wrote: > Currently, neither is enabled globally but may be enabled on a per-VCPU > basis by the altp2m code. > > Everything can be force-disabled globally by specifying vmfunc=0 on the > Xen command line. > > Remove the check for EPTE bit 63 == zero in ept_split_super_pa

[Xen-devel] [PATCH 01/11] VMX: VMFUNC and #VE definitions and detection.

2015-01-09 Thread Ed White
Currently, neither is enabled globally but may be enabled on a per-VCPU basis by the altp2m code. Everything can be force-disabled globally by specifying vmfunc=0 on the Xen command line. Remove the check for EPTE bit 63 == zero in ept_split_super_page(), as that bit is now hardware-defined. Sig