Re: [PATCH 00/15] Device Evidence and Trust for PCI Security Protocol (TDISP)
Xu Yilun <[email protected]> Tue, 4 Aug 2026 09:48:30 +0800
| Newsgroups | dev.linux.lists.linux-coco,dev.linux.lists.driver-core,org.kernel.vger.linux-pci |
|---|---|
| Message-ID | <anFE7m164AmchTy/@yilunxu-OptiPlex-7050> |
On Tue, Jul 28, 2026 at 08:29:35PM -0300, Jason Gunthorpe wrote: > On Tue, Jul 28, 2026 at 06:20:10PM +1000, Alexey Kardashevskiy wrote: > > On 6/7/26 08:08, Dan Williams wrote: > > > Major changes since: "[PATCH v2 00/19] PCI/TSM: TEE I/O infrastructure" [1] > > > > soo with the recent sudden sad news about Dan, I do not know where to start really so I just start... > > > > Here is his unfinished work which I'd really like to see finished to > > progress with the phase2 of the plan. How do we proceed from now on? > > Yes, we do, but at least I need some more time before considering what > to do, sorry. > > > The direction appears to be set, imho the immediate TODO list is: > > - address "not-netlink-y enough" concerns > > - teach pci_iomap() to map mixed private+shared BARs (ones which contain MSIX for the starter) > > - always call pci_tsm_ops::enable_dma/disable_dma > > - ditch the module trust parameter? > > - add a knob to enable/disable DMA and keep TDI in RUN > > I somehow suspect we should probably reduce the scope somewhat into > smaller chunks at a time and try to follow this as a skeleton, but I > haven't studied it carefully. Hi Jason & Ankit: 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? https://zoom-lfx.platform.linuxfoundation.org/meeting/93219227394?password=80705486-101a-4e19-8f11-0baaf92104be