Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2

2021-02-04 Thread Quentin Perret
On Wednesday 03 Feb 2021 at 16:11:47 (+), Will Deacon wrote: > On Fri, Jan 08, 2021 at 12:15:24PM +, Quentin Perret wrote: > > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > > to give the hypervisor some control over the host memory accesses. At > > the moment all

Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2

2021-02-04 Thread Will Deacon
On Thu, Feb 04, 2021 at 02:26:35PM +, Quentin Perret wrote: > On Wednesday 03 Feb 2021 at 16:11:47 (+), Will Deacon wrote: > > On Fri, Jan 08, 2021 at 12:15:24PM +, Quentin Perret wrote: > > > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > > > to give the

Re: [RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2

2021-02-03 Thread Will Deacon
On Fri, Jan 08, 2021 at 12:15:24PM +, Quentin Perret wrote: > When KVM runs in protected nVHE mode, make use of a stage 2 page-table > to give the hypervisor some control over the host memory accesses. At > the moment all memory aborts from the host will be instantly idmapped > RWX at stage 2

[RFC PATCH v2 26/26] KVM: arm64: Wrap the host with a stage 2

2021-01-08 Thread Quentin Perret
When KVM runs in protected nVHE mode, make use of a stage 2 page-table to give the hypervisor some control over the host memory accesses. At the moment all memory aborts from the host will be instantly idmapped RWX at stage 2 in a lazy fashion. Later patches will make use of that infrastructure to