[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86y10bpph8.wl-maz@kernel.org>
Date: Thu, 19 Dec 2024 17:11:31 +0000
From: Marc Zyngier <maz@...nel.org>
To: Ard Biesheuvel <ardb+git@...gle.com>
Cc: linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Ard Biesheuvel <ardb@...nel.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Ryan Roberts <ryan.roberts@....com>,
Anshuman Khandual <anshuman.khandual@....com>,
Kees Cook <keescook@...omium.org>,
Quentin Perret <qperret@...gle.com>
Subject: Re: [PATCH v3 0/6] arm64: Clean up and simplify PA space size handling
On Thu, 12 Dec 2024 08:18:42 +0000,
Ard Biesheuvel <ardb+git@...gle.com> wrote:
>
> From: Ard Biesheuvel <ardb@...nel.org>
>
> This series addresses a number of buglets related to how we handle the
> size of the physical address space when building LPA2 capable kernels:
>
> - reject 52-bit physical addressess in the mapping routines when LPA2 is
> configured but not available at runtime
> - ensure that TCR.IPS is not set to 52-bits if LPA2 is not supported
> - ensure that TCR_EL2.PS and DS match the host, regardless of whether
> LPA2 is available at stage 2
> - don't rely on kvm_get_parange() and invalid physical addresses as
> control flags in the pKVM page donation APIs
>
> Finally, the configurable 48-bit physical address space limit is dropped
> entirely, as it doesn't buy us a lot now that all the PARange and {I}PS
> handling is done at runtime.
Acked-by: Marc Zyngier <maz@...nel.org>
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists