All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"yilun.xu@linux.intel.com" <yilun.xu@linux.intel.com>,
	"x86@kernel.org" <x86@kernel.org>
Cc: "Gao, Chao" <chao.gao@intel.com>,
	"Xu, Yilun" <yilun.xu@intel.com>,
	"Duan, Zhenzhong" <zhenzhong.duan@intel.com>,
	"kas@kernel.org" <kas@kernel.org>,
	"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
	"Li, Xiaoyao" <xiaoyao.li@intel.com>,
	"Maloor, Kishen" <kishen.maloor@intel.com>,
	"Hunter, Adrian" <adrian.hunter@intel.com>,
	"tony.lindgren@linux.intel.com" <tony.lindgren@linux.intel.com>,
	"Mehta, Sohil" <sohil.mehta@intel.com>,
	"Fang, Peter" <peter.fang@intel.com>,
	"nik.borisov@suse.com" <nik.borisov@suse.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"artem.bityutskiy@linux.intel.com"
	<artem.bityutskiy@linux.intel.com>
Subject: Re: [PATCH v2 0/5] Enable TDX module extensions
Date: Tue, 15 Sep 2026 22:09:54 +0000	[thread overview]
Message-ID: <20df772d83f42efdc0ec69a5a3ffb15e91910b85.camel@intel.com> (raw)
In-Reply-To: <20260915102658.713079-1-yilun.xu@linux.intel.com>

On Tue, 2026-09-15 at 18:26 +0800, Xu Yilun wrote:
> This is based on v7.3-rc1. You can find the full branch stack at [2].
> The DICE part is in the full branch as an example for extensions. But it
> does not include the other DICE feedbacks.
> 
> The full branch contains:
> 
>   Dependency:  Patch 1:   SEAMCALL version patch [3] which is WIP on
> 			  community review.
>   This series: Patch 2~7: This series, including this cover-letter.
>   Use case:    Patch 8~N: The old DICE part as an example.

A downside to these stacks is that we don't get Sashiko review. I wonder if it
would pick this up:
https://b4.docs.kernel.org/en/latest/contributor/prep.html#using-the-message-id

      parent reply	other threads:[~2026-09-15 22:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-15 10:26 [PATCH v2 0/5] Enable TDX module extensions Xu Yilun
2026-09-15 10:26 ` [PATCH v2 1/5] x86/virt/tdx: Move TDH.SYS.CONFIG operations into a wrapper Xu Yilun
2026-09-15 20:45   ` Edgecombe, Rick P
2026-09-18  9:54     ` Xu Yilun
2026-09-22  7:09   ` Tony Lindgren
2026-09-15 10:26 ` [PATCH v2 2/5] x86/virt/tdx: Configure add-on features on TDX module init Xu Yilun
2026-09-15 20:54   ` Edgecombe, Rick P
2026-09-21 11:42     ` Xu Yilun
2026-09-22 14:48       ` Edgecombe, Rick P
2026-09-24  1:51         ` Xu Yilun
2026-09-16  3:23   ` Chao Gao
2026-09-18  9:56     ` Xu Yilun
2026-09-22  7:13   ` Tony Lindgren
2026-09-23  7:30     ` Xu Yilun
2026-09-23  7:59       ` Tony Lindgren
2026-09-24  1:33         ` Xu Yilun
2026-09-24  6:22           ` Tony Lindgren
2026-09-25 14:12   ` Nikolay Borisov
2026-09-15 10:26 ` [PATCH v2 3/5] x86/virt/tdx: Detect if the extensions initialization is required Xu Yilun
2026-09-15 21:14   ` Edgecombe, Rick P
2026-09-18  9:58     ` Xu Yilun
2026-09-28 21:06     ` Edgecombe, Rick P
2026-09-29  9:28       ` Xu Yilun
2026-09-29 16:33         ` Edgecombe, Rick P
2026-09-29 17:26   ` Nikolay Borisov
2026-09-30  3:02     ` Xu Yilun
2026-09-15 10:26 ` [PATCH v2 4/5] x86/virt/tdx: Add extra memory to TDX module for the extensions Xu Yilun
2026-09-15 21:19   ` Edgecombe, Rick P
2026-10-01 12:14     ` Kiryl Shutsemau
2026-10-01 14:55       ` Edgecombe, Rick P
2026-09-16  7:40   ` Chao Gao
2026-09-18 10:06     ` Xu Yilun
2026-09-22  7:25   ` Tony Lindgren
2026-09-15 10:26 ` [PATCH v2 5/5] x86/virt/tdx: Make TDX module initialize " Xu Yilun
2026-09-15 22:09 ` Edgecombe, Rick P [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20df772d83f42efdc0ec69a5a3ffb15e91910b85.camel@intel.com \
    --to=rick.p.edgecombe@intel.com \
    --cc=adrian.hunter@intel.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=baolu.lu@linux.intel.com \
    --cc=chao.gao@intel.com \
    --cc=kas@kernel.org \
    --cc=kishen.maloor@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nik.borisov@suse.com \
    --cc=peter.fang@intel.com \
    --cc=sohil.mehta@intel.com \
    --cc=tony.lindgren@linux.intel.com \
    --cc=x86@kernel.org \
    --cc=xiaoyao.li@intel.com \
    --cc=yilun.xu@intel.com \
    --cc=yilun.xu@linux.intel.com \
    --cc=zhenzhong.duan@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.