From: "Kalra, Ashish" <ashish.kalra@amd.com>
To: Michael Roth <michael.roth@amd.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>,
linux-tip-commits@vger.kernel.org, bp@alien8.de, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/sev: Apply RMP table fixups for kexec.
Date: Wed, 3 Apr 2024 16:08:35 -0500 [thread overview]
Message-ID: <ff810b13-b534-4e4f-a2e2-3cdf2b563494@amd.com> (raw)
In-Reply-To: <20240402224222.vxaqenqvyi32zleb@amd.com>
On 4/2/2024 5:42 PM, Michael Roth wrote:
> On Tue, Apr 02, 2024 at 05:31:09PM -0500, Kalra, Ashish wrote:
>> On 4/2/2024 5:09 PM, Tom Lendacky wrote:
>>> On 3/12/24 13:47, Ashish Kalra wrote:
>>>> From: Ashish Kalra <ashish.kalra@amd.com>
>>>>
>>>> RMP table start and end physical range may not be aligned to 2MB in
>>>> the e820 tables causing fatal RMP page faults during kexec boot when
>>>> new page allocations are done in the same 2MB page as the RMP table.
>>>> Check if RMP table start and end physical range in e820_table is not
>>>> aligned to 2MB and in that case use e820__range_update() to map this
>>>> range to reserved.
>>>>
>>>> Override e820__memory_setup_default() to check and apply these RMP table
>>>> fixups in e820_table before e820_table is used to setup
>>>> e280_table_firmware and e820_table_kexec.
>>>>
>>>> Fixes: c3b86e61b756 ("x86/cpufeatures: Enable/unmask SEV-SNP CPU
>>>> feature")
>>>> Signed-off-by: Ashish Kalra <ashish.kalra@amd.com>
>>>> ---
>>>> arch/x86/virt/svm/sev.c | 52 +++++++++++++++++++++++++++++++++++++++++
>>>> 1 file changed, 52 insertions(+)
>>>>
>>>> diff --git a/arch/x86/virt/svm/sev.c b/arch/x86/virt/svm/sev.c
>>>> index cffe1157a90a..e0d7584df28f 100644
>>>> --- a/arch/x86/virt/svm/sev.c
>>>> +++ b/arch/x86/virt/svm/sev.c
>>>> @@ -65,6 +65,8 @@ static u64 probed_rmp_base, probed_rmp_size;
>>>> static struct rmpentry *rmptable __ro_after_init;
>>>> static u64 rmptable_max_pfn __ro_after_init;
>>>> +static char *__init snp_rmptable_e820_fixup(void);
>>>> +
>>>> static LIST_HEAD(snp_leaked_pages_list);
>>>> static DEFINE_SPINLOCK(snp_leaked_pages_list_lock);
>>>> @@ -160,9 +162,59 @@ bool snp_probe_rmptable_info(void)
>>>> pr_info("RMP table physical range [0x%016llx - 0x%016llx]\n",
>>>> probed_rmp_base, probed_rmp_base + probed_rmp_size - 1);
>>>> + /*
>>>> + * Override e820__memory_setup_default() to do any RMP table fixups
>>>> + * for kexec if required.
>>>> + */
>>>> + x86_init.resources.memory_setup = snp_rmptable_e820_fixup;
>>> This produces a build warning:
>>>
>>> WARNING: modpost: vmlinux: section mismatch in reference:
>>> snp_probe_rmptable_info+0x95 (section: .text) -> x86_init (section:
>>> .init.data)
>>> WARNING: modpost: vmlinux: section mismatch in reference:
>>> snp_probe_rmptable_info+0x99 (section: .text) -> snp_rmptable_e820_fixup
>>> (section: .init.text)
>>>
>> Oh, so this requires snp_probe_rmptable_info() to be fixed to use the __init
>> macro.
>>
>> I believe that snp_probe_rmptable_info() should be anyway using the __init
>> macro and this fix for snp_probe_rmptable_info() needs to be sent as a
>> separate patch and regardless of this patch getting merged or not.
> I think you'll hit issues with:
>
> bsp_determine_snp() -> //non-__init
> snp_probe_rmptable_info() //__init
>
> and bsp_determine_snp() sticks around as a function pointer assigned to
> cpuinfo_x86 so I don't think you can use __init there.
>
> So might need to just drop __init from snp_rmptable_e820_fixup().
Actually, that will not help as snp_probe_rmptable_info() is *also*
accessing x86_init.resources.memory_setup
Thanks, Ashish
>
>> Thanks, Ashish
>>
>>> Thanks,
>>> Tom
>>>
>>>> +
>>>> return true;
>>>> }
next prev parent reply other threads:[~2024-04-03 21:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 18:47 [PATCH] x86/sev: Apply RMP table fixups for kexec Ashish Kalra
2024-03-13 10:58 ` Aithal, Srikanth
2024-04-02 14:45 ` bp
2024-04-02 15:54 ` Tom Lendacky
2024-04-02 16:34 ` bp
2024-04-02 17:06 ` Kalra, Ashish
2024-04-02 17:11 ` Kalra, Ashish
2024-04-02 17:45 ` Borislav Petkov
2024-04-02 18:41 ` Kalra, Ashish
2024-04-02 18:50 ` Borislav Petkov
2024-04-02 19:33 ` Kalra, Ashish
2024-04-02 20:21 ` Borislav Petkov
2024-04-02 21:00 ` Kalra, Ashish
2024-04-02 21:17 ` Kalra, Ashish
2024-04-02 21:20 ` Borislav Petkov
2024-04-02 21:31 ` Kalra, Ashish
2024-04-02 21:40 ` Borislav Petkov
2024-04-02 22:09 ` Tom Lendacky
2024-04-02 22:31 ` Kalra, Ashish
2024-04-02 22:42 ` Michael Roth
2024-04-03 21:08 ` Kalra, Ashish [this message]
2024-04-04 8:17 ` Jeremi Piotrowski
2024-04-04 18:07 ` Kalra, Ashish
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=ff810b13-b534-4e4f-a2e2-3cdf2b563494@amd.com \
--to=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=michael.roth@amd.com \
--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