From: Liam Merwick <liam.merwick@oracle.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>,
Liam Merwick <liam.merwick@oracle.com>
Subject: Re: [PATCH] x86/sev: Do RMP memory coverage check after max_pfn has been set
Date: Thu, 6 Jun 2024 13:09:05 +0000 [thread overview]
Message-ID: <47f963f7-86ee-442a-8446-bb40b19869e9@oracle.com> (raw)
In-Reply-To: <92b4ba20a5afeb4aecde167bfac094d0275d8e1b.1717601917.git.thomas.lendacky@amd.com>
On 05/06/2024 16:38, Tom Lendacky wrote:
> The RMP table is probed early in the boot process before max_pfn has been
> set, so the logic to check if the RMP covers all of system memory is not
> valid.
>
> Move the RMP memory coverage check from snp_probe_rmptable_info() into
> snp_rmptable_init(), which is well after max_pfn has been set.
>
> Fixes: 216d106c7ff7 ("x86/sev: Add SEV-SNP host initialization support")
> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
> ---
> arch/x86/virt/svm/sev.c | 45 ++++++++++++++++++++---------------------
> 1 file changed, 22 insertions(+), 23 deletions(-)
>
next prev parent reply other threads:[~2024-06-06 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 15:38 [PATCH] x86/sev: Do RMP memory coverage check after max_pfn has been set Tom Lendacky
2024-06-06 13:09 ` Liam Merwick [this message]
2024-06-21 13:59 ` Borislav Petkov
2024-06-21 14:17 ` Tom Lendacky
2024-06-21 14:29 ` Borislav Petkov
2024-06-21 14:37 ` Tom Lendacky
2024-06-21 14:49 ` Borislav Petkov
2024-06-21 15:02 ` Tom Lendacky
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=47f963f7-86ee-442a-8446-bb40b19869e9@oracle.com \
--to=liam.merwick@oracle.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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