Re: [PATCH v11 3/6] x86/sev: Initialize RMPOPT configuration MSRs
Borislav Petkov <[email protected]> Thu, 30 Jul 2026 17:12:38 -0700
| Newsgroups | org.kernel.vger.linux-crypto,dev.linux.lists.linux-coco,org.kernel.vger.kvm,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <20260731001238.GMamvodtFAY7Scdtha@fat_crate.local> |
On Thu, Jul 30, 2026 at 03:00:55PM -0500, Kalra, Ashish wrote:
> No hard dependency =E2=80=94 it only needs SNP initialized (post
> SNP_INIT_EX/DF_FLUSH), and the initial pass is async anyway, so it's
> independent of the SEV-TIO block and the panic notifier. So i can move =
it to
> the end (after the TIO block so it runs last without touching TIO order=
ing),
> but is there a specific reason you want me to move it to the end, as it=
can
> just stay here after SNP_INIT.
The usual reason is, you add new code at the end. I.e., you append it. Th=
at is
usually easier for backporting too.
When you put it *NOT* at the end, then the first question I have is, why =
is
this thing there? Is there a particular reason for it to be there? Is ord=
ering
important all of a sudden?
--=20
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette