From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Tom Lendacky <thomas.lendacky@amd.com>,
Dionna Amalie Glaze <dionnaglaze@google.com>,
Kevin Loughlin <kevinloughlin@google.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-efi@vger.kernel.org, x86@kernel.org
Subject: Re: [tip: x86/boot] x86/boot/sev: Avoid shared GHCB page for early memory acceptance
Date: Fri, 18 Apr 2025 10:14:40 +0200 [thread overview]
Message-ID: <aAIJ8C5Ho97geYMj@gmail.com> (raw)
In-Reply-To: <aAICRcfkBV3tHP-G@gmail.com>
* Ingo Molnar <mingo@kernel.org> wrote:
>
> * Ard Biesheuvel <ardb@kernel.org> wrote:
>
> > On Sat, 12 Apr 2025 at 22:45, Ingo Molnar <mingo@kernel.org> wrote:
> > >
> > >
> > > * Ard Biesheuvel <ardb@kernel.org> wrote:
> > >
> > > > On Sat, 12 Apr 2025 at 22:29, tip-bot2 for Ard Biesheuvel
> > > > <tip-bot2@linutronix.de> wrote:
> > > > >
> > > > > The following commit has been merged into the x86/boot branch of tip:
> > > > >
> > > >
> > > > This may be slightly premature. I took some of Tom's code, hence the
> > > > co-developed-by, but the should really confirm that what I did is
> > > > correct before we queue this up.
> > >
> > > OK, I've zapped it again, especially as the rest of the series wasn't
> > > ready either, please include the latest version of this patch as part
> > > of the boot/setup/ series, which hard-relies upon it.
> > >
> >
> > I have sent out a v4 here [0].
> >
> > I am not including it in the next rev of the startup/ refactor series,
> > given that this change is a fix that also needs to go to stable.
> > Please apply it as a fix and merge back the branch into tip/x86/boot -
> > I will rebase the startup/ refactor series on top of that.
> >
> > Thanks,
> >
> > [0] https://lore.kernel.org/linux-efi/20250417202120.1002102-2-ardb+git@google.com/T/#u
>
> Noted, thanks for the heads up!
So there's this new merge commit in tip:x86/boot:
54f71aa90c84 Merge branch 'x86/urgent' into x86/boot, to merge dependent commit and fixes
which brings this fix into x86/boot:
a718833cb456 ("x86/boot/sev: Avoid shared GHCB page for early memory acceptance")
thus 54f71aa90c84 should be a proper base the rest of the startup/
series, right?
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-18 8:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 13:28 [PATCH v3] x86/boot/sev: Avoid shared GHCB page for early memory acceptance Ard Biesheuvel
2025-04-11 18:41 ` Borislav Petkov
2025-04-11 19:00 ` Ard Biesheuvel
2025-04-11 19:11 ` Borislav Petkov
2025-04-17 16:08 ` Tom Lendacky
2025-04-17 16:14 ` Ard Biesheuvel
2025-04-17 16:21 ` Tom Lendacky
2025-04-17 16:38 ` Ard Biesheuvel
2025-04-17 17:26 ` Tom Lendacky
2025-04-17 20:01 ` Tom Lendacky
2025-04-17 20:17 ` Ard Biesheuvel
2025-04-18 7:43 ` Ingo Molnar
2025-04-12 20:29 ` [tip: x86/boot] " tip-bot2 for Ard Biesheuvel
2025-04-12 20:33 ` Ard Biesheuvel
2025-04-12 20:45 ` Ingo Molnar
2025-04-12 20:50 ` Ard Biesheuvel
2025-04-18 7:12 ` Ard Biesheuvel
2025-04-18 7:41 ` Ingo Molnar
2025-04-18 8:14 ` Ingo Molnar [this message]
2025-04-18 11:42 ` 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=aAIJ8C5Ho97geYMj@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=dionnaglaze@google.com \
--cc=kevinloughlin@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.