From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: catalin.marinas@arm.com, will@kernel.org, maz@kernel.org,
anshuman.khandual@arm.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: booting: Require placement within 48-bit addressable memory
Date: Mon, 14 Nov 2022 13:37:30 +0000 [thread overview]
Message-ID: <Y3JEmqyv0HMraW5K@FVFF77S0Q05N> (raw)
In-Reply-To: <CAMj1kXFuo8z+okLFvU3yHdP1h37NG8jkq6BL+N17tgJHMpd-nw@mail.gmail.com>
On Mon, Nov 14, 2022 at 02:33:52PM +0100, Ard Biesheuvel wrote:
> On Mon, 14 Nov 2022 at 13:10, Mark Rutland <mark.rutland@arm.com> wrote:
> >
> > On Mon, Nov 14, 2022 at 12:58:10PM +0100, Ard Biesheuvel wrote:
> > > + Bit 3-4 Kernel physical placement
> > >
> > > 0
> > > 2MB aligned base should be as close as possible
> > > to the base of DRAM, since memory below it is not
> > > accessible via the linear mapping
> > > 1
> > > + 2MB aligned base such that base plus image_size is
> > > + entirely within the 48-bit addressable range
> >
> > This seems to assume text_offset is zero (which is the case today, but this is
> > the first part of booting.txt that assumes that); as a matter of policy are we
> > sure that we'll never use a non-zero offset again? If so, we probably want to
> > mention that in the "header notes" section, or come up with some wording to
> > include it here.
> >
>
> How about:
>
> 2MB aligned base such that all image_size bytes
> counted from the start of the image are within
> the 48-bit addressable range
>
> ?
Sounds good to me, thanks!
Mark.
_______________________________________________
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-14 13:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 11:58 [PATCH] arm64: booting: Require placement within 48-bit addressable memory Ard Biesheuvel
2022-11-14 12:10 ` Mark Rutland
2022-11-14 13:33 ` Ard Biesheuvel
2022-11-14 13:37 ` Mark Rutland [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 17:02 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
2022-11-25 13:24 ` Will Deacon
2022-11-30 12:32 ` Ard Biesheuvel
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=Y3JEmqyv0HMraW5K@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--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