From: Aneesh Kumar K.V <aneesh.kumar@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>,
linux-coco@lists.linux.dev, linux-pci@vger.kernel.org
Cc: aik@amd.com, yilun.xu@linux.intel.com, bhelgaas@google.com,
gregkh@linuxfoundation.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Samuel Ortiz" <sameo@rivosinc.com>
Subject: Re: [PATCH v7 0/9] PCI/TSM: Core infrastructure for PCI device security (TDISP)
Date: Mon, 27 Oct 2025 15:31:06 +0530 [thread overview]
Message-ID: <yq5azf9coe8t.fsf@kernel.org> (raw)
In-Reply-To: <20251024020418.1366664-1-dan.j.williams@intel.com>
Dan Williams <dan.j.williams@intel.com> writes:
> Changes since v6 [1]:
> - Rebase on v6.18-rc2
> - Drop @owner from 'struct pci_tsm' and lookup @ops through @tsm_dev
> (Alexey)
> - Drop CONFIG_PCI_IDE_STREAM_MAX, only require pci_ide_set_nr_streams()
> for host bridge implementations that limit streams to something less
> than topology max (Aneesh)
> - Convert Stream index allocators from bitmaps to ida (preparation for
> solving Stream ID uniqueness problem reported by Alexey)
> - Misc whitespace cleanups (Jonathan)
> - Misc kdoc fixups
> - Fix nr_ide_streams data type, a u8 is too small
> - Rename PCI_DOE_PROTO_ => PCI_DOE_FEATURE_ (Alexey)
> - Rename @base to @base_tsm in 'struct pci_tsm_pf0' (Aneesh)
> - Fix up PCIe r6.1 reference for PCIe r7.0 (Bjorn)
> - Fix to_pci_tsm_pf0() failing to walk to the DSM device (Yilun)
> - Add pci_tsm_fn_exit() for sub-function cleanups post DSM disconnect
> (Aneesh)
> - Move the samples/devsec/ implementation to a follow-on patch set
>
> [1]: http://lore.kernel.org/20250911235647.3248419-1-dan.j.williams@intel.com
>
> This set is available at
> https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/log/?h=staging
> (rebasing branch) or devsec-20251023 (immutable tag). That branch
> additionally contains address association support, Stream ID uniqueness
> compability quirk, updated samples/devsec/ (now with multifunction
> device and simple bind support), and an updated preview of v2 of "[PATCH
> 0/7] PCI/TSM: TEE I/O infrastructure" (fixes x86 encrypted ioremap and
> other changes) [2].
>
> [2]: http://lore.kernel.org/20250827035259.1356758-1-dan.j.williams@intel.com
>
> It passes an updated regression testing using samples/devsec/. See this
> commit on the staging branch for that test:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/commit/?id=44932bffdcc1
>
> Status: ->connect() flow is settled
> -----------------------------------
> At the risk of tempting fate, the goal is this v7 goes to linux-next via
> a stable tsm.git#next branch. Enable one or more TSM driver
> implementations to queue on top for v6.19-rc1 via arch-specific trees
> for TDX, TIO, CCA, or COVE-IO. I.e. target v6.19 to support baseline
> link encryption (IDE) / secure-session establishment without
> confidential device-assignment.
>
> That tsm.git#next goal still needs follow-on patches like the following
> to settle:
>
> Alexey Kardashevskiy (1):
> PCI/IDE: Initialize an ID for all IDE streams
>
> Xu Yilun (1):
> PCI/IDE: Add Address Association Register setup for downstream MMIO
>
> ...but otherwise the core infrastructure is ready to support IDE
> establishment via a platform TSM.
>
> Next steps:
> -----------
> - Stage at least one vendor ->connect() implementation on top of a
> tsm.git#staging snapshot, for integration testing.
>
> - Additionally get at least one vendor ->connect() implementation queued
> in an arch tree for linux-next in time for v6.19, otherwise
> tsm.git#next may need to wait for v6.20.
>
Arm CCA changes can be found https://lore.kernel.org/all/20251027095602.1154418-2-aneesh.kumar@kernel.org
-aneesh
next prev parent reply other threads:[~2025-10-27 10:01 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 2:04 [PATCH v7 0/9] PCI/TSM: Core infrastructure for PCI device security (TDISP) Dan Williams
2025-10-24 2:04 ` [PATCH v7 1/9] coco/tsm: Introduce a core device for TEE Security Managers Dan Williams
2025-10-29 13:33 ` Jonathan Cameron
2025-10-29 23:47 ` dan.j.williams
2025-10-30 1:00 ` Alexey Kardashevskiy
2025-10-30 9:04 ` Carlos López
2025-10-30 23:16 ` dan.j.williams
2025-10-24 2:04 ` [PATCH v7 2/9] PCI/IDE: Enumerate Selective Stream IDE capabilities Dan Williams
2025-10-29 13:42 ` Jonathan Cameron
2025-10-29 23:55 ` dan.j.williams
2025-10-30 0:59 ` Alexey Kardashevskiy
2025-10-30 21:13 ` dan.j.williams
2025-10-30 21:37 ` Bjorn Helgaas
2025-10-30 23:56 ` Alexey Kardashevskiy
2025-10-31 0:34 ` dan.j.williams
2025-10-31 1:20 ` Bjorn Helgaas
2025-10-30 8:34 ` Aneesh Kumar K.V
2025-10-24 2:04 ` [PATCH v7 3/9] PCI: Introduce pci_walk_bus_reverse(), for_each_pci_dev_reverse() Dan Williams
2025-10-29 14:00 ` Jonathan Cameron
2025-10-29 16:05 ` dan.j.williams
2025-10-30 19:36 ` dan.j.williams
2025-10-24 2:04 ` [PATCH v7 4/9] PCI/TSM: Establish Secure Sessions and Link Encryption Dan Williams
2025-10-26 3:18 ` kernel test robot
2025-10-29 15:53 ` Jonathan Cameron
2025-10-30 19:56 ` dan.j.williams
2025-10-30 1:13 ` Alexey Kardashevskiy
2025-10-30 8:35 ` Aneesh Kumar K.V
2025-10-24 2:04 ` [PATCH v7 5/9] PCI: Add PCIe Device 3 Extended Capability enumeration Dan Williams
2025-10-24 2:04 ` [PATCH v7 6/9] PCI: Establish document for PCI host bridge sysfs attributes Dan Williams
2025-10-29 16:04 ` Jonathan Cameron
2025-10-24 2:04 ` [PATCH v7 7/9] PCI/IDE: Add IDE establishment helpers Dan Williams
2025-10-25 16:53 ` Aneesh Kumar K.V
2025-10-29 18:57 ` dan.j.williams
2025-10-29 16:25 ` Jonathan Cameron
2025-10-24 2:04 ` [PATCH v7 8/9] PCI/IDE: Report available IDE streams Dan Williams
2025-10-29 16:31 ` Jonathan Cameron
2025-10-30 20:48 ` dan.j.williams
2025-10-24 2:04 ` [PATCH v7 9/9] PCI/TSM: Report active " Dan Williams
2025-10-29 16:34 ` Jonathan Cameron
2025-10-30 21:03 ` dan.j.williams
2025-10-30 2:05 ` Alexey Kardashevskiy
2025-10-27 10:01 ` Aneesh Kumar K.V [this message]
2025-10-29 5:20 ` [PATCH v7 0/9] PCI/TSM: Core infrastructure for PCI device security (TDISP) Alexey Kardashevskiy
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=yq5azf9coe8t.fsf@kernel.org \
--to=aneesh.kumar@kernel.org \
--cc=aik@amd.com \
--cc=bhelgaas@google.com \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-pci@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sameo@rivosinc.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 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.