From: <dan.j.williams@intel.com>
To: Xu Yilun <yilun.xu@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-pci@vger.kernel.org>, <linux-coco@lists.linux.dev>,
<gregkh@linuxfoundation.org>, <aik@amd.com>,
<aneesh.kumar@kernel.org>, "Lukas Wunner" <lukas@wunner.de>,
Samuel Ortiz <sameo@rivosinc.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: Re: [PATCH v8 4/9] PCI/TSM: Establish Secure Sessions and Link Encryption
Date: Mon, 10 Nov 2025 15:19:36 -0800 [thread overview]
Message-ID: <691273081685_1d9110038@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <aRFfk14DJWEVhC/R@yilunxu-OptiPlex-7050>
Xu Yilun wrote:
> > +#ifdef CONFIG_PCI_TSM
> > +int pci_tsm_register(struct tsm_dev *tsm_dev);
> > +void pci_tsm_unregister(struct tsm_dev *tsm_dev);
> > +int pci_tsm_link_constructor(struct pci_dev *pdev, struct pci_tsm *tsm,
> > + struct tsm_dev *tsm_dev);
> > +int pci_tsm_pf0_constructor(struct pci_dev *pdev, struct pci_tsm_pf0 *tsm,
> > + struct tsm_dev *tsm_dev);
> > +void pci_tsm_pf0_destructor(struct pci_tsm_pf0 *tsm);
> > +int pci_tsm_doe_transfer(struct pci_dev *pdev, u8 type, const void *req,
> > + size_t req_sz, void *resp, size_t resp_sz);
> > +#else
> > +static inline int pci_tsm_register(struct tsm_dev *tsm_dev)
> > +{
> > + return 0;
> > +}
> > +static inline void pci_tsm_unregister(struct tsm_dev *tsm_dev)
> > +{
> > +}
> > +static inline int pci_tsm_doe_transfer(struct pci_dev *pdev, u8 type,
> > + const void *req, size_t req_sz,
> > + void *resp, size_t resp_sz)
>
> Any concern to keep the stub without PCI_TSM?
> pci_tsm_pf0_constructor/destructor() don't do this.
True. There should be no callers of this when CONFIG_PCI_TSM=n. Will
append a cleanup for this.
>
> > +{
> > + return -ENXIO;
> > +}
> > +#endif
>
> [...]
>
> > diff --git a/drivers/pci/tsm.c b/drivers/pci/tsm.c
> > new file mode 100644
> > index 000000000000..6a2849f77adc
> > --- /dev/null
> > +++ b/drivers/pci/tsm.c
> > @@ -0,0 +1,643 @@
> > +// SPDX-License-Identifier: GPL-2.0
> > +/*
> > + * Interface with platform TEE Security Manager (TSM) objects as defined by
> > + * PCIe r7.0 section 11 TEE Device Interface Security Protocol (TDISP)
> > + *
> > + * Copyright(c) 2024-2025 Intel Corporation. All rights reserved.
> > + */
> > +
> > +#define dev_fmt(fmt) "PCI/TSM: " fmt
> > +
> > +#include <linux/bitfield.h>
>
> No need the bitfield.h
>
> > +#include <linux/pci.h>
> > +#include <linux/pci-doe.h>
> > +#include <linux/pci-tsm.h>
> > +#include <linux/sysfs.h>
> > +#include <linux/tsm.h>
> > +#include <linux/xarray.h>
>
> No need the xarray.h
>
> Anyway, they are all minor and cause no impact, I don't expect a new
> version.
Ah yes, holdovers from early versions, will append your reviewed-by in
the pull request.
>
> Reviewed-by: Xu Yilun <yilun.xu@linux.intel.com>
>
next prev parent reply other threads:[~2025-11-10 22:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 21:28 [PATCH v8 0/9] PCI/TSM: Core infrastructure for PCI device security (TDISP) Dan Williams
2025-10-31 21:28 ` [PATCH v8 1/9] coco/tsm: Introduce a core device for TEE Security Managers Dan Williams
2025-11-08 15:45 ` Xu Yilun
2025-10-31 21:28 ` [PATCH v8 2/9] PCI/IDE: Enumerate Selective Stream IDE capabilities Dan Williams
2025-11-08 16:15 ` Xu Yilun
2025-10-31 21:28 ` [PATCH v8 3/9] PCI: Introduce pci_walk_bus_reverse(), for_each_pci_dev_reverse() Dan Williams
2025-10-31 21:28 ` [PATCH v8 4/9] PCI/TSM: Establish Secure Sessions and Link Encryption Dan Williams
2025-11-10 3:44 ` Xu Yilun
2025-11-10 23:19 ` dan.j.williams [this message]
2025-10-31 21:28 ` [PATCH v8 5/9] PCI: Add PCIe Device 3 Extended Capability enumeration Dan Williams
2025-11-10 3:45 ` Xu Yilun
2025-10-31 21:28 ` [PATCH v8 6/9] PCI: Establish document for PCI host bridge sysfs attributes Dan Williams
2025-10-31 21:28 ` [PATCH v8 7/9] PCI/IDE: Add IDE establishment helpers Dan Williams
2025-11-03 15:04 ` Jonathan Cameron
2025-11-10 4:16 ` Xu Yilun
2025-11-10 23:21 ` dan.j.williams
2025-10-31 21:29 ` [PATCH v8 8/9] PCI/IDE: Report available IDE streams Dan Williams
2025-11-10 4:49 ` Xu Yilun
2025-11-10 23:49 ` dan.j.williams
2025-10-31 21:29 ` [PATCH v8 9/9] PCI/TSM: Report active " Dan Williams
2025-11-10 4:52 ` Xu Yilun
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=691273081685_1d9110038@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).