Re: [RFC PATCH 03/13] kvm: Add XO memslot type

2019-10-06 Thread Paolo Bonzini
On 04/10/19 21:06, Edgecombe, Rick P wrote: > The reasoning was that it seems like KVM leaves it to userspace to control the > physical address space layout since userspace decides the supported physical > address bits and lays out memory in the physical address space. So duplication > with XO mems

Re: [RFC PATCH 03/13] kvm: Add XO memslot type

2019-10-04 Thread Edgecombe, Rick P
On Fri, 2019-10-04 at 09:27 +0200, Paolo Bonzini wrote: > On 03/10/19 23:23, Rick Edgecombe wrote: > > Add XO memslot type to create execute-only guest physical memory based on > > the RO memslot. Like the RO memslot, disallow changing the memslot type > > to/from XO. > > > > In the EPT case ACC_U

Re: [RFC PATCH 03/13] kvm: Add XO memslot type

2019-10-04 Thread Paolo Bonzini
On 03/10/19 23:23, Rick Edgecombe wrote: > Add XO memslot type to create execute-only guest physical memory based on > the RO memslot. Like the RO memslot, disallow changing the memslot type > to/from XO. > > In the EPT case ACC_USER_MASK represents the readable bit, so add the > ability for set_s

[RFC PATCH 03/13] kvm: Add XO memslot type

2019-10-03 Thread Rick Edgecombe
Add XO memslot type to create execute-only guest physical memory based on the RO memslot. Like the RO memslot, disallow changing the memslot type to/from XO. In the EPT case ACC_USER_MASK represents the readable bit, so add the ability for set_spte() to unset this. This is based in part on a patc