From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alexey Kardashevskiy <aik@amd.com>
Cc: Xu Yilun <yilun.xu@linux.intel.com>,
ankita@nvidia.com, linux-coco@lists.linux.dev,
linux-pci@vger.kernel.org, driver-core@lists.linux.dev,
Aaron Tomlin <atomlin@atomlin.com>,
Alistair Francis <alistair.francis@wdc.com>,
"Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Daniel Gomez <da.gomez@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Dexuan Cui <decui@microsoft.com>,
Donald Hunter <donald.hunter@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jakub Kicinski <kuba@kernel.org>,
Luis Chamberlain <mcgrof@kernel.org>,
Lukas Wunner <lukas@wunner.de>, Petr Pavlu <petr.pavlu@suse.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Sami Tolvanen <samitolvanen@google.com>,
Samuel Ortiz <sameo@rivosinc.com>,
Saravana Kannan <saravanak@google.com>,
Will Deacon <will@kernel.org>,
"Fontenot, Nathan" <Nathan.Fontenot@amd.com>,
rick.p.edgecombe@intel.com, yilun.xu@intel.com,
Jiri Pirko <jiri@resnulli.us>, Leon Romanovsky <leon@kernel.org>
Subject: Re: [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP)
Date: Wed, 2 Sep 2026 12:01:25 -0300 [thread overview]
Message-ID: <20260902150125.GD2890729@ziepe.ca> (raw)
In-Reply-To: <2e721509-0aee-47ee-b17a-688876e02f74@amd.com>
On Wed, Sep 02, 2026 at 12:20:51PM +1000, Alexey Kardashevskiy wrote:
> On 2/9/26 12:12, Xu Yilun wrote:
> > On Tue, Aug 04, 2026 at 09:55:33PM -0300, Jason Gunthorpe wrote:
> > > On Tue, Aug 04, 2026 at 09:48:30AM +0800, Xu Yilun wrote:
> > >
> > > > Glad to see you all here to make progress! Intel can also help on this.
> > > > Can we have a meeting to discuss on these topics? As Alexey mentioned,
> > > > previously we had a bi-weekly call, perhaps use that for our first
> > > > meeting? Or what time works best for everyone?
> > >
> > > I prefer we defer such community discussions till September, that
> > > seems appropriate given some dates I've seen.
> >
> > Hi Ankit & Jason,
> >
> > Do we have a plan to schedule a meeting to discuss next steps?
> >
> > If so, we can figure out a specific time on the Discord channel.
> > https://discord.gg/KKqC438c
> So I've been trying to find a time slot. Say, keep it on Thursdays
> (USA) (kinda short notice), bi-weekly, we can do:
I've asked several people in Europe to help on parts of this series,
and combined with China/Aus someone is going to end up left out.
I know people are anxious about their projects. In the short term I
will volunteer to send patches (ie bug fixes!) to Linus in the CC area
Dan was responsible for. Please email me if something needs some
attention and we can figure it out.
To fully move forward we need to establish a new TSM maintainer
team. In my past experience a consensus has emerged off list, I
suggest we try that here as well. Several people should be
recruited. I will also volunteer to help train and launch a new team.
I can say that several people from NVIDIA are working on the ideas in
this patch series. Ankit is setting up a team to focus on upstream
patches for all of CC inside NVIDIA. I've asked Jiri Pirko to work on
the PCI evidence uAPI based on his deep netlink experience, and Leon
Romanovsky to work on the binding problem/adversarial/trust level
driver core idea. They will share their approaches for solving these
problems as seperate proposals.
> Scenario A:
> Seattle (PDT, UTC-7) 07:00 – 08:00 Day 1
> Atlantic Time (ADT, UTC-3) 11:00 – 12:00 Day 1
> Berlin (CEST, UTC+2) 16:00 – 17:00 Day 1
> India (IST, UTC+5:30) 19:30 – 20:30 Day 1
> China (CST, UTC+8) 22:00 – 23:00 Day 1
> Sydney (AEST, UTC+10) 00:00 – 01:00 Day 2 (I can do it once in 2 weeks)
This is the only time Europe could reasonably participate in,
obviously it is not OK for China and Aus.
> Please, comment. I find these calls pretty productive syncups. So
> far we were not having Europe in these calls.
Calls are undoutably useful!
> Alternatively, wait until the LPC in a month but I suspect not
> everybody is going to be there.
LPC is not that far away, I think we should have a goal of having a
consensus for or at LPC
Regards,
Jason
next prev parent reply other threads:[~2026-09-02 15:01 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 22:08 [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Dan Williams
2026-07-05 22:08 ` [PATCH 01/15] netlink: specs: Introduce multi-message blobs for SPDM Dan Williams
2026-07-08 11:13 ` Donald Hunter
2026-07-11 1:43 ` Dan Williams (nvidia)
2026-07-08 13:23 ` Donald Hunter
2026-07-22 1:20 ` Jakub Kicinski
2026-08-02 17:58 ` Ankit Agrawal
2026-08-03 16:35 ` Jakub Kicinski
2026-07-05 22:08 ` [PATCH 02/15] tools: ynl: Teach pyynl to handle blobs Dan Williams
2026-07-08 13:48 ` Donald Hunter
2026-07-05 22:08 ` [PATCH 03/15] tools: ynl: Teach ynl_gen_c to validate and dump 'blob' attributes Dan Williams
2026-07-05 22:08 ` [PATCH 04/15] device core: Introduce "device evidence" over netlink Dan Williams
2026-07-08 13:22 ` Donald Hunter
2026-07-05 22:08 ` [PATCH 05/15] device core: Add "device evidence" 'validate' command Dan Williams
2026-07-05 22:08 ` [PATCH 06/15] PCI/TSM: Add device evidence support Dan Williams
2026-07-08 5:00 ` Alexey Kardashevskiy
2026-07-08 18:25 ` Dan Williams (nvidia)
2026-07-05 22:08 ` [PATCH 07/15] modules: Document the global async_probe parameter Dan Williams
2026-07-17 13:44 ` Nikolay Borisov
2026-07-05 22:08 ` [PATCH 08/15] device core: Initial device trust infrastructure Dan Williams
2026-07-06 13:45 ` Jason Gunthorpe
2026-07-05 22:08 ` [PATCH 09/15] PCI, device core: Move "untrusted" concept to DEVICE_TRUST_ADVERSARY Dan Williams
2026-07-06 13:49 ` Jason Gunthorpe
2026-07-07 13:04 ` Robin Murphy
2026-07-05 22:08 ` [PATCH 10/15] PCI/TSM: Add device interface security LOCKED support Dan Williams
2026-07-05 22:08 ` [PATCH 11/15] PCI/TSM: Add device interface security RUN support Dan Williams
2026-07-05 22:08 ` [PATCH 12/15] PCI/TSM: Add device interface security DMA enable/disable Dan Williams
2026-07-05 22:08 ` [PATCH 13/15] PCI, device core: Add private memory access for DEVICE_TRUST_TCB Dan Williams
2026-07-06 12:42 ` Aneesh Kumar K.V
2026-07-08 18:06 ` Dan Williams (nvidia)
2026-07-08 18:10 ` Aneesh Kumar K.V
2026-07-09 6:32 ` Alexey Kardashevskiy
2026-07-09 7:38 ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 14/15] PCI/TSM: Create MMIO descriptors via TDISP Report Dan Williams
2026-07-08 9:49 ` Alexey Kardashevskiy
2026-07-05 22:08 ` [PATCH 15/15] PCI/TSM: Add relative MMIO offset support? Dan Williams
2026-07-08 2:25 ` Alexey Kardashevskiy
2026-07-08 18:05 ` Dan Williams (nvidia)
2026-07-06 12:51 ` [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP) Jason Gunthorpe
2026-07-06 20:55 ` Dan Williams (nvidia)
2026-07-07 12:43 ` Jason Gunthorpe
2026-07-08 0:12 ` Dan Williams (nvidia)
2026-07-08 14:31 ` Jason Gunthorpe
2026-07-09 2:45 ` Dan Williams (nvidia)
2026-07-09 13:36 ` Jason Gunthorpe
2026-07-15 9:04 ` Alexey Kardashevskiy
2026-07-16 18:51 ` Jason Gunthorpe
2026-07-28 8:20 ` Alexey Kardashevskiy
2026-07-28 23:29 ` Jason Gunthorpe
2026-08-04 1:48 ` Xu Yilun
2026-08-04 20:33 ` Ankit Agrawal
2026-08-05 17:43 ` Xu Yilun
2026-08-05 0:55 ` Jason Gunthorpe
2026-09-02 2:12 ` Xu Yilun
2026-09-02 2:20 ` Alexey Kardashevskiy
2026-09-02 7:28 ` Leon Romanovsky
2026-09-02 9:30 ` Xu Yilun
2026-09-02 15:01 ` Jason Gunthorpe [this message]
2026-09-03 2:21 ` Alexey Kardashevskiy
2026-09-03 5:59 ` Aneesh Kumar K.V
2026-09-03 6:51 ` Leon Romanovsky
2026-09-03 8:11 ` Ankit Agrawal
2026-09-03 11:04 ` Ankit Agrawal
2026-09-03 13:36 ` Lukas Wunner
2026-09-03 15:05 ` Dave Hansen
2026-09-03 17:53 ` Jason Gunthorpe
2026-09-03 20:02 ` Jonathan Cameron
2026-09-04 9:52 ` Jiri Pirko
2026-07-29 1:57 ` Ankit Agrawal
2026-08-02 18:12 ` Ankit Agrawal
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=20260902150125.GD2890729@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Nathan.Fontenot@amd.com \
--cc=aik@amd.com \
--cc=alistair.francis@wdc.com \
--cc=aneesh.kumar@kernel.org \
--cc=ankita@nvidia.com \
--cc=arnd@arndb.de \
--cc=atomlin@atomlin.com \
--cc=bhelgaas@google.com \
--cc=da.gomez@kernel.org \
--cc=dakr@kernel.org \
--cc=decui@microsoft.com \
--cc=donald.hunter@gmail.com \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mcgrof@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=rafael@kernel.org \
--cc=rick.p.edgecombe@intel.com \
--cc=robin.murphy@arm.com \
--cc=sameo@rivosinc.com \
--cc=samitolvanen@google.com \
--cc=saravanak@google.com \
--cc=will@kernel.org \
--cc=yilun.xu@intel.com \
--cc=yilun.xu@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox