Re: [Xen-devel] [PATCH v2] x86-64/Xen: eliminate W+X mappings

2017-12-18 Thread Joe Perches
On Mon, 2017-12-18 at 13:28 +0100, Ingo Molnar wrote: > * Jan Beulich wrote: > > > A few thousand such pages are usually left around due to the re-use of > > L1 tables having been provided by the hypervisor (Dom0) or tool stack > > (DomU). Set NX in the direct map variant, which needs to be done

Re: [Xen-devel] [PATCH v2] x86-64/Xen: eliminate W+X mappings

2017-12-18 Thread Ingo Molnar
* Jan Beulich wrote: > A few thousand such pages are usually left around due to the re-use of > L1 tables having been provided by the hypervisor (Dom0) or tool stack > (DomU). Set NX in the direct map variant, which needs to be done in L2 > due to the dual use of the re-used L1s. > > For x86_co

Re: [Xen-devel] [PATCH v2] x86-64/Xen: eliminate W+X mappings

2017-12-18 Thread Juergen Gross
On 18/12/17 12:11, Jan Beulich wrote: > A few thousand such pages are usually left around due to the re-use of > L1 tables having been provided by the hypervisor (Dom0) or tool stack > (DomU). Set NX in the direct map variant, which needs to be done in L2 > due to the dual use of the re-used L1s. >

[Xen-devel] [PATCH v2] x86-64/Xen: eliminate W+X mappings

2017-12-18 Thread Jan Beulich
A few thousand such pages are usually left around due to the re-use of L1 tables having been provided by the hypervisor (Dom0) or tool stack (DomU). Set NX in the direct map variant, which needs to be done in L2 due to the dual use of the re-used L1s. For x86_configure_nx() to actually do what it