linux-kernel - Re: [PATCH] x86/sev: Apply RMP table fixups for kexec.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240402214036.GFZgx7VBVD1qwp7RKT@fat_crate.local>
Date: Tue, 2 Apr 2024 23:40:36 +0200
From: Borislav Petkov <bp@...en8.de>
To: "Kalra, Ashish" <ashish.kalra@....com>
Cc: bp@...nel.org, thomas.lendacky@....com, linux-kernel@...r.kernel.org,
	linux-tip-commits@...r.kernel.org, michael.roth@....com,
	x86@...nel.org
Subject: Re: [PATCH] x86/sev: Apply RMP table fixups for kexec.

On Tue, Apr 02, 2024 at 04:31:30PM -0500, Kalra, Ashish wrote:
> The main issue is there is no API interface available to do that, i will
> need to add new API interfaces to update the e820_table_kexec and
> e820_table_firmware and then will that be acceptable for a use case which
> can be handled via a platform specific quirk ?

I can't review a patch without seeing it first, sorry.

> Yes exactly, that's what the above comment means.
> 
>  That's why the above commit message says "may".

Yah, *never* use "may" in commit messages. This is internal speak and
doesn't belong in the kernel. Your commit message need to explain stuff
fully and properly. Otherwise I'll keep asking until it does.

> My point is that we always keep the RMP table memory reserved regardless of
> SNP enablement, so these are simply fixups/adjustments on top of that
> reservation.

Yes.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette