From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>, Ashish Kalra <Ashish.Kalra@amd.com>
Cc: tglx@kernel.org, mingo@redhat.com, dave.hansen@linux.intel.com,
x86@kernel.org, hpa@zytor.com, luto@kernel.org,
peterz@infradead.org, ardb@kernel.org, rppt@kernel.org,
akpm@linux-foundation.org, arnd@arndb.de, shivankg@amd.com,
linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev
Subject: Re: [PATCH v2] x86/sev: Apply the RMP table e820 fixups before memblock is populated
Date: Wed, 21 Oct 2026 08:41:12 -0500 [thread overview]
Message-ID: <3bf62eea-5ddd-4551-896c-5e95f168429c@amd.com> (raw)
In-Reply-To: <20261021034913.GBatg2OToG0uQD7FvZ@fat_crate.local>
On 10/20/26 22:49, Borislav Petkov wrote:
> On Tue, Oct 20, 2026 at 08:28:18PM +0000, Ashish Kalra wrote:
>> From: Ashish Kalra <ashish.kalra@amd.com>
>>
>> When the start and/or end of the RMP table is not 2MB aligned,
>
> When is that the case? Why aren't they? Why doesn't firmware align them?
It is actually quite common with the contiguous RMP and a bit less with
the segmented RMP as the RMP segments tend to be aligned, but the RMP
segment table tends not to be.
We can ask BIOS to do this in the future, but we have a lot of existing
versions of BIOS out there that don't do this and require this support.
Thanks,
Tom
>
prev parent reply other threads:[~2026-10-21 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 20:28 Ashish Kalra
2026-10-21 3:49 ` Borislav Petkov
2026-10-21 13:41 ` Tom Lendacky [this message]
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=3bf62eea-5ddd-4551-896c-5e95f168429c@amd.com \
--to=thomas.lendacky@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=shivankg@amd.com \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®