linux-kernel - Re: [PATCH 5/5] x86/virt/tdx: Export global metadata read infrastructure

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]

Date: Mon, 6 May 2024 08:43:52 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kai Huang <kai.huang@...el.com>, linux-kernel@...r.kernel.org,
 kvm@...r.kernel.org
Cc: x86@...nel.org, kirill.shutemov@...ux.intel.com, peterz@...radead.org,
 tglx@...utronix.de, bp@...en8.de, mingo@...hat.com, hpa@...or.com,
 seanjc@...gle.com, pbonzini@...hat.com, isaku.yamahata@...el.com,
 jgross@...e.com
Subject: Re: [PATCH 5/5] x86/virt/tdx: Export global metadata read
 infrastructure

On 3/1/24 03:20, Kai Huang wrote:
> KVM will need to read a bunch of non-TDMR related metadata to create and
> run TDX guests.  Export the metadata read infrastructure for KVM to use.

All of this hinges on how KVM ends up using this infrastructure.

I want to see the whole picture before _any_ of this gets applied.
These 5 patches only vaguely hint at that bigger picture.

I know folks want to draw some kind of line and say "x86" over here and
"kvm" over there.  But that inclination really doesn't help anyone get
that big picture view.