[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aQVt9hk0d4u1IU7S@intel.com>
Date: Sat, 1 Nov 2025 10:18:30 +0800
From: Chao Gao <chao.gao@...el.com>
To: Vishal Annapurve <vannapurve@...gle.com>
CC: Sagi Shahar <sagis@...gle.com>, <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>, <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
>> > == 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"?
>>
>
>Hi Chao,
>
>Is this non-RFC series dependent on RFC patches?
>
>What's the intended order of upstreaming the features and dependencies
>being discussed here?
Features are expected to be merged in this order:
1. Move VMXON out of KVM
2. tdx-host device
3. TDX Module version exposure, i.e., https://lore.kernel.org/linux-coco/20251001022309.277238-1-chao.gao@intel.com/
4. TDX Module runtime update
Powered by blists - more mailing lists