[PATCH v3 26/32] KVM: arm64: Introduce PROT_NONE mappings for stage 2

2021-03-02 Thread Quentin Perret
Once we start unmapping portions of memory from the host stage 2 (such as e.g. the hypervisor memory sections, or pages that belong to protected guests), we will need a way to track page ownership. And given that all mappings in the host stage 2 will be identity-mapped, we can use the host stage 2

Re: [PATCH v3 26/32] KVM: arm64: Introduce PROT_NONE mappings for stage 2

2021-03-04 Thread Will Deacon
On Tue, Mar 02, 2021 at 02:59:56PM +, Quentin Perret wrote: > Once we start unmapping portions of memory from the host stage 2 (such > as e.g. the hypervisor memory sections, or pages that belong to > protected guests), we will need a way to track page ownership. And > given that all mappings i

Re: [PATCH v3 26/32] KVM: arm64: Introduce PROT_NONE mappings for stage 2

2021-03-05 Thread Quentin Perret
On Thursday 04 Mar 2021 at 20:00:45 (+), Will Deacon wrote: > On Tue, Mar 02, 2021 at 02:59:56PM +, Quentin Perret wrote: > > Once we start unmapping portions of memory from the host stage 2 (such > > as e.g. the hypervisor memory sections, or pages that belong to > > protected guests), we

Re: [PATCH v3 26/32] KVM: arm64: Introduce PROT_NONE mappings for stage 2

2021-03-05 Thread Will Deacon
On Fri, Mar 05, 2021 at 09:52:12AM +, Quentin Perret wrote: > On Thursday 04 Mar 2021 at 20:00:45 (+), Will Deacon wrote: > > On Tue, Mar 02, 2021 at 02:59:56PM +, Quentin Perret wrote: > > > Once we start unmapping portions of memory from the host stage 2 (such > > > as e.g. the hyperv