[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXGiy4XU0nrPU9UL3C1KHDznim1gj=P-MabVu=D59k3Fww@mail.gmail.com>
Date: Tue, 2 Sep 2025 14:24:31 +0200
From: Ard Biesheuvel <ardb@...nel.org>
To: Borislav Petkov <bp@...en8.de>
Cc: Ard Biesheuvel <ardb+git@...gle.com>, linux-kernel@...r.kernel.org,
linux-efi@...r.kernel.org, x86@...nel.org, Ingo Molnar <mingo@...nel.org>,
Kevin Loughlin <kevinloughlin@...gle.com>, Tom Lendacky <thomas.lendacky@....com>,
Josh Poimboeuf <jpoimboe@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
Nikunj A Dadhania <nikunj@....com>
Subject: Re: [PATCH v7 12/22] x86/sev: Provide PIC aliases for SEV related
data objects
On Tue, 2 Sept 2025 at 14:07, Borislav Petkov <bp@...en8.de> wrote:
>
> On Thu, Aug 28, 2025 at 12:22:15PM +0200, Ard Biesheuvel wrote:
> > From: Ard Biesheuvel <ardb@...nel.org>
> >
> > Provide PIC aliases for data objects that are shared between the SEV
> > startup code and the SEV code that executes later. This is needed so
> > that the confined startup code is permitted to access them.
> >
> > This requires some of these variables to be moved into a source file
> > that is not part of the startup code, as the PIC alias is already
> > implied, and exporting variables in the opposite direction is not
> > supported.
> >
> > Move ghcb_version as well, but don't provide a PIC alias as it is not
> > actually needed.
>
> I see
>
> SYM_PIC_ALIAS(ghcb_version);
>
> below.
>
> Stale commit message?
>
Yes, as a result of
https://lore.kernel.org/all/20250530165507.GBaDni69NqgOi4mFNn@fat_crate.local/
it was exported but I failed to update the commit log accordingly.
Powered by blists - more mailing lists