[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXG4umHx6ebVRjg-C+_xJRRBrxmqhiDKqVychCPF9PJoGQ@mail.gmail.com>
Date: Thu, 24 Apr 2025 20:17:27 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Ingo Molnar <mingo@...nel.org>
Cc: Ard Biesheuvel <ardb+git@...gle.com>, linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [RFC PATCH PoC 01/11] x86/linkage: Add SYM_PI_ALIAS() macro
helper to emit symbol aliases
On Thu, 24 Apr 2025 at 20:05, Ingo Molnar <mingo@...nel.org> wrote:
>
>
> * Ard Biesheuvel <ardb+git@...gle.com> wrote:
>
> > From: Ard Biesheuvel <ardb@...nel.org>
> >
> > Startup code that may execute from the early 1:1 mapping of memory will
> > be confined into its own address space, and only be permitted to access
> > ordinary kernel symbols if this is known to be safe.
> >
> > Introduce a macro helper PI_ALIAS() that emits a __pi_ prefixed alias
> > for a symbol, which allows startup code to access it.
>
> s/PI_ALIAS
> /SYM_PI_ALIAS
>
> What does 'PI' stand for? 'Physical memory Identity' map?
>
'position independent' - it's what we ended up with on arm64, but I'm
not attached to it so happy to switch to something better.
Powered by blists - more mailing lists