From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>, linux-arm-kernel@lists.infradead.org
Cc: will@kernel.org, catalin.marinas@arm.com, mark.rutland@arm.com
Subject: Re: [PATCH] arm64: booting: Require placement within 48-bit addressable memory
Date: Wed, 23 Nov 2022 18:56:19 +0530 [thread overview]
Message-ID: <1b4e77d3-555e-41e5-2511-21f20a76ddb2@arm.com> (raw)
In-Reply-To: <20221122170249.2453853-1-ardb@kernel.org>
On 11/22/22 22:32, Ard Biesheuvel wrote:
> Some configurations (i.e., 64k + LVA/LPA) can tolerate a physical
> placement of the kernel image outside of the 48-bit addressable region,
> but given that the loader has no way of knowing whether or not the image
> in question supports LVA/LPA, it currently has no choice but to place it
> below the 48-bit mark.
>
> Once we add support for LPA2, which allows 52-bit physical and virtual
> addressing when using 4k or 16k pages, but in way that relies on
> increasing the number of paging levels, there will be more variety in
> the configurations that may or may not support this.
>
> So redefine bit #3 in the Image header as 'must be placed within 48-bit
> addressable memory', as this is the current de facto meaning.
>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
Regardless of possible vmlinux beyond 48 bits physical address discussion,
this patch looks good, and complete in itself.
Reviewed-by: Anshuman Khandual <anshuman.khandual@arm.com>
> Documentation/arm64/booting.rst | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/arm64/booting.rst b/Documentation/arm64/booting.rst
> index 8c324ad638de2b27..5a764fabfea821f0 100644
> --- a/Documentation/arm64/booting.rst
> +++ b/Documentation/arm64/booting.rst
> @@ -121,8 +121,9 @@ Header notes:
> to the base of DRAM, since memory below it is not
> accessible via the linear mapping
> 1
> - 2MB aligned base may be anywhere in physical
> - memory
> + 2MB aligned base such that all image_size bytes
> + counted from the start of the image are within
> + the 48-bit addressable range of physical memory
> Bits 4-63 Reserved.
> ============= ===============================================================
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-11-23 13:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 17:02 [PATCH] arm64: booting: Require placement within 48-bit addressable memory Ard Biesheuvel
2022-11-22 17:03 ` Ard Biesheuvel
2022-11-23 6:29 ` Anshuman Khandual
2022-11-23 8:28 ` Ard Biesheuvel
2022-11-22 17:05 ` Mark Rutland
2022-11-23 13:26 ` Anshuman Khandual [this message]
2022-11-25 13:24 ` Will Deacon
2022-11-30 12:32 ` Ard Biesheuvel
-- strict thread matches above, loose matches on Subject: below --
2022-11-14 11:58 Ard Biesheuvel
2022-11-14 12:10 ` Mark Rutland
2022-11-14 13:33 ` Ard Biesheuvel
2022-11-14 13:37 ` Mark Rutland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1b4e77d3-555e-41e5-2511-21f20a76ddb2@arm.com \
--to=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).