linux-kernel - Re: [PATCH v2 00/21] Runtime TDX Module update support

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: <aQVq9tzQ1McNi/Mx@intel.com>
Date: Sat, 1 Nov 2025 10:05:42 +0800
From: Chao Gao <chao.gao@...el.com>
To: Sagi Shahar <sagis@...gle.com>
CC: <linux-coco@...ts.linux.dev>, <linux-kernel@...r.kernel.org>,
	<x86@...nel.org>, <reinette.chatre@...el.com>, <ira.weiny@...el.com>,
	<kai.huang@...el.com>, <dan.j.williams@...el.com>,
	<yilun.xu@...ux.intel.com>, <vannapurve@...gle.com>, <paulmck@...nel.org>,
	<nik.borisov@...e.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen
	<dave.hansen@...ux.intel.com>, "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar
	<mingo@...hat.com>, "Kirill A. Shutemov" <kas@...nel.org>, Paolo Bonzini
	<pbonzini@...hat.com>, Rick Edgecombe <rick.p.edgecombe@...el.com>, "Thomas
 Gleixner" <tglx@...utronix.de>
Subject: Re: [PATCH v2 00/21] Runtime TDX Module update support

>> == How to test this series ==
>>
>> This series can be tested using the userspace tool that is able to
>> select the appropriate TDX module and install it via the interfaces
>> exposed by this series:
>>
>>  # git clone https://github.com/intel/tdx-module-binaries
>>  # cd tdx-module-binaries
>>  # python version_select_and_load.py --update
>>
>> == Base commit ==
>>
>> This series is based on:
>> https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/commit/?h=tdx&id=9332e088937f
>
>Can you clarify which patches are needed from this tree? Is it just
>"coco/tdx-host: Introduce a "tdx_host" device" or is this series also
>depends on other patches?
>
>More specifically, does this series depend on "Move VMXON/VMXOFF
>handling from KVM to CPU lifecycle"?

Yes. I meant checkout to that specific commit. both "tdx_host" device and
"Move VMXOFF handling from KVM to CPU lifecycle" are needed to apply this
series.