linux-kernel - Re: [PATCH v8 00/30] TDX KVM selftests

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: <CAAhR5DFFRRV9hH3VOmZqb6TArcZL0=893oi3M2rZgVC5Bu-vJg@mail.gmail.com>
Date: Thu, 14 Aug 2025 23:14:42 -0500
From: Sagi Shahar <sagis@...gle.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Rick P Edgecombe <rick.p.edgecombe@...el.com>, Erdem Aktas <erdemaktas@...gle.com>, 
	"kvm@...r.kernel.org" <kvm@...r.kernel.org>, "shuah@...nel.org" <shuah@...nel.org>, 
	Ryan Afranji <afranji@...gle.com>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Reinette Chatre <reinette.chatre@...el.com>, 
	"binbin.wu@...ux.intel.com" <binbin.wu@...ux.intel.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>, 
	"ackerleytng@...gle.com" <ackerleytng@...gle.com>, Isaku Yamahata <isaku.yamahata@...el.com>, 
	"pratikrajesh.sampat@....com" <pratikrajesh.sampat@....com>, Ira Weiny <ira.weiny@...el.com>, 
	Roger Wang <runanwang@...gle.com>, 
	"linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>, 
	"ajones@...tanamicro.com" <ajones@...tanamicro.com>, "oliver.upton@...ux.dev" <oliver.upton@...ux.dev>
Subject: Re: [PATCH v8 00/30] TDX KVM selftests

On Mon, Aug 11, 2025 at 3:53 PM Sean Christopherson <seanjc@...gle.com> wrote:
>
> On Mon, Aug 11, 2025, Rick P Edgecombe wrote:
> > But Sean, if you want to save some time I think we can just accelerate this
> > other reviewing. As far as new-fangled features, having this upstream is
> > important even for that, because we are currently having to keep these tests
> > plus follow on tests in sync across various development branches. So yea, it's
> > time to get this over the line.
>
> Yes please.  The unspoken threat in my response is that at some point I will just
> start NAKing KVM TDX patches :-D

I'm making good progress and the massive refactor is mostly complete.
I believe I should have the patches ready to review next week.

I'm also thinking that it would be easier if I split the series in 2
or possibly 3 patchset. The first one including the setup code and the
basic lifecycle test and then the rest of the tests with possibly the
guest_memfd tests in a separate series. What do you think?