linux-kernel - Re: [PATCH v9 09/19] x86: Secure Launch kernel late boot stub

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: <D1RLIGJ6FYTA.4JNBEUEDEY9P@kernel.org>
Date: Wed, 05 Jun 2024 01:45:17 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: <ross.philipson@...cle.com>, <linux-kernel@...r.kernel.org>,
 <x86@...nel.org>, <linux-integrity@...r.kernel.org>,
 <linux-doc@...r.kernel.org>, <linux-crypto@...r.kernel.org>,
 <kexec@...ts.infradead.org>, <linux-efi@...r.kernel.org>,
 <iommu@...ts.linux-foundation.org>
Cc: <dpsmith@...rtussolutions.com>, <tglx@...utronix.de>,
 <mingo@...hat.com>, <bp@...en8.de>, <hpa@...or.com>,
 <dave.hansen@...ux.intel.com>, <ardb@...nel.org>, <mjg59@...f.ucam.org>,
 <James.Bottomley@...senpartnership.com>, <peterhuewe@....de>,
 <jgg@...pe.ca>, <luto@...capital.net>, <nivedita@...m.mit.edu>,
 <herbert@...dor.apana.org.au>, <davem@...emloft.net>, <corbet@....net>,
 <ebiederm@...ssion.com>, <dwmw2@...radead.org>, <baolu.lu@...ux.intel.com>,
 <kanth.ghatraju@...cle.com>, <andrew.cooper3@...rix.com>,
 <trenchboot-devel@...glegroups.com>
Subject: Re: [PATCH v9 09/19] x86: Secure Launch kernel late boot stub

On Wed Jun 5, 2024 at 12:16 AM EEST,  wrote:
> On 6/4/24 12:58 PM, Jarkko Sakkinen wrote:
> > On Fri May 31, 2024 at 4:03 AM EEST, Ross Philipson wrote:
> >> The routine slaunch_setup is called out of the x86 specific setup_arch()
> >> routine during early kernel boot. After determining what platform is
> >> present, various operations specific to that platform occur. This
> >> includes finalizing setting for the platform late launch and verifying
> >> that memory protections are in place.
> > 
> > "memory protections" is not too helpful tbh.
> > 
> > Better to describe very briefly the VT-d usage.
>
> We can enhance the commit message and talk about VT-d usage and what 
> PMRs are and do.

Yep, pointing out exact things that you're dealing with is even more
useful once the feature has landed.

After some months one tends to start forgetting things, so it is good
to use commit messages as clues and reminders of essential concepts.

BR, Jarkko