From: Tom Lendacky <thomas.lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Michael Roth <michael.roth@amd.com>,
Ashish Kalra <ashish.kalra@amd.com>
Subject: Re: [PATCH] x86/sev: Do RMP memory coverage check after max_pfn has been set
Date: Fri, 21 Jun 2024 10:02:30 -0500 [thread overview]
Message-ID: <e41238d2-5a20-5497-76ee-4eaa39d3df89@amd.com> (raw)
In-Reply-To: <20240621144956.GJZnWTFLIwvAxy7bMr@fat_crate.local>
On 6/21/24 09:49, Borislav Petkov wrote:
> On Fri, Jun 21, 2024 at 09:37:46AM -0500, Tom Lendacky wrote:
>> Ok, I'll remove the new static and resubmit. There is also a logic error
>> in the original check which should be using PFN_UP instead of PHYS_PFN, so
>> I'll include that, too.
>
> So we said this fix should not go to stable because SNP host is not upstream
> yet.
Correct.
>
>> Do you want a single patch or two patches, one to fix the PHYS_PFN to
>> PFN_UP and one to move the check?
>
> Since this is snp_rmptable_init() and that is also SNP host then I think
> a single patch is fine.
Will do.
Thanks,
Tom
>
> Thx.
>
prev parent reply other threads:[~2024-06-21 15:02 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
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 [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=e41238d2-5a20-5497-76ee-4eaa39d3df89@amd.com \
--to=thomas.lendacky@amd.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=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