From: Ingo Molnar <mingo@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
Borislav Petkov <bp@alien8.de>,
Ard Biesheuvel <ardb+git@google.com>,
linux-efi@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dionna Amalie Glaze <dionnaglaze@google.com>,
Kevin Loughlin <kevinloughlin@google.com>
Subject: Re: [PATCH v3] x86/boot/sev: Avoid shared GHCB page for early memory acceptance
Date: Fri, 18 Apr 2025 09:43:28 +0200 [thread overview]
Message-ID: <aAICoBecodJfFXMk@gmail.com> (raw)
In-Reply-To: <CAMj1kXH4e3cFBZaaLpNqiE6A-T-zAKqfuSOuRX-Zz+M=e2Fr2Q@mail.gmail.com>
* Ard Biesheuvel <ardb@kernel.org> wrote:
> > >> OK. Would this do the trick? (with asm/sev.h added to the #includes)
> > >
> > > Yes, that works for booting. Let me do some kexec testing and get back
> > > to you. Sorry, that might not be until tomorrow, though.
> >
> > Ok, found some time... looks good with kexec, too.
> >
>
> Thanks!
I've turned this into this tag for the -v4 patch:
Tested-by: Tom Lendacky <thomas.lendacky@amd.com>
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-18 7:43 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 [this message]
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
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=aAICoBecodJfFXMk@gmail.com \
--to=mingo@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--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=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 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).