From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>,
x86@kernel.org, linux-coco@lists.linux.dev,
linux-kernel@vger.kernel.org
Cc: dave.hansen@linux.intel.com, tglx@kernel.org, mingo@redhat.com,
bp@alien8.de, hpa@zytor.com, dave.hansen@intel.com,
kas@kernel.org, rick.p.edgecombe@intel.com, jgg@nvidia.com,
nicolinc@nvidia.com, aik@amd.com, aneesh.kumar@kernel.org,
seanjc@google.com, pbonzini@redhat.com, yilun.xu@linux.intel.com,
chao.gao@intel.com, vishal.l.verma@intel.com,
kevin.tian@intel.com, chao.p.peng@intel.com
Subject: Re: [RFC PATCH 04/15] virt: tdx-guest: Support devsec TSM for secure devices
Date: Mon, 26 Oct 2026 09:12:07 +0800 [thread overview]
Message-ID: <59b997ce-f5b9-4a3b-9de8-91533289bfe7@intel.com> (raw)
In-Reply-To: <20260924041032.1096569-5-zhenzhong.duan@intel.com>
On 9/24/2026 12:10 PM, Zhenzhong Duan wrote:
> Register Intel TDX secure device (devsec TSM) to the TSM framework and
> supply the tdx_devsec_ops callback operations. This enables control and
> management of the Trust Device Interface (TDI) through those hooks in
> accordance with the TDISP protocol.
It only implements the placeholders for these hooks. Please state them accurately.
> Check the TDCS configuration flags during driver initialization to
> ensure the hardware interface is supported before attempting device
> registration.
>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> arch/x86/include/asm/shared/tdx.h | 1 +
> drivers/virt/coco/tdx-guest/Kconfig | 15 ++++
> drivers/virt/coco/tdx-guest/Makefile | 3 +
> drivers/virt/coco/tdx-guest/connect.c | 81 +++++++++++++++++++
> .../coco/tdx-guest/{tdx-guest.c => main.c} | 6 ++
> drivers/virt/coco/tdx-guest/tdx-guest.h | 20 +++++
> 6 files changed, 126 insertions(+)
> create mode 100644 drivers/virt/coco/tdx-guest/connect.c
> rename drivers/virt/coco/tdx-guest/{tdx-guest.c => main.c} (98%)
> create mode 100644 drivers/virt/coco/tdx-guest/tdx-guest.h
>
> diff --git a/arch/x86/include/asm/shared/tdx.h b/arch/x86/include/asm/shared/tdx.h
> index 665c12925ff6..499103f7a01b 100644
> --- a/arch/x86/include/asm/shared/tdx.h
> +++ b/arch/x86/include/asm/shared/tdx.h
> @@ -56,6 +56,7 @@
>
> /* TDCS_CONFIG_FLAGS bits */
> #define TDCS_CONFIG_FLEXIBLE_PENDING_VE BIT_ULL(1)
> +#define TDCS_CONFIG_TDX_CONNECT BIT_ULL(5)
>
> /* TDCS_TD_CTLS bits */
> #define TD_CTLS_PENDING_VE_DISABLE_BIT 0
> diff --git a/drivers/virt/coco/tdx-guest/Kconfig b/drivers/virt/coco/tdx-guest/Kconfig
> index dbbdc14383b1..2e9407f8bc70 100644
> --- a/drivers/virt/coco/tdx-guest/Kconfig
> +++ b/drivers/virt/coco/tdx-guest/Kconfig
> @@ -10,3 +10,18 @@ config TDX_GUEST_DRIVER
>
> To compile this driver as module, choose M here. The module will
> be called tdx-guest.
> +
> +config TDX_CONNECT_GUEST
> + bool "Intel TDX Connect Guest Support"
> + depends on TDX_GUEST_DRIVER
maybe select TDX_GUEST_DRIVER ?
> + depends on PCI_TSM
> + default y
> + help
> + Support Trust Device Interface (TDI) feature enumeration,
> + validation, and activation within an Intel TDX guest.
> +
> + This option enables the guest kernel to establish secure,
> + isolated connections with trusted devices assigned to the TD,
> + validating MMIO maps and authorizing DMA remapping tables.
> +
> + If unsure, say Y.
> diff --git a/drivers/virt/coco/tdx-guest/Makefile b/drivers/virt/coco/tdx-guest/Makefile
> index 775cb463f9c8..cfa991c7aeb5 100644
> --- a/drivers/virt/coco/tdx-guest/Makefile
> +++ b/drivers/virt/coco/tdx-guest/Makefile
> @@ -1,2 +1,5 @@
> # SPDX-License-Identifier: GPL-2.0
> obj-$(CONFIG_TDX_GUEST_DRIVER) += tdx-guest.o
> +
> +tdx-guest-y := main.o
> +tdx-guest-$(CONFIG_TDX_CONNECT_GUEST) += connect.o
> diff --git a/drivers/virt/coco/tdx-guest/connect.c b/drivers/virt/coco/tdx-guest/connect.c
> new file mode 100644
> index 000000000000..80ae7c19e179
> --- /dev/null
> +++ b/drivers/virt/coco/tdx-guest/connect.c
> @@ -0,0 +1,81 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * TDX Connect guest driver
> + *
> + * Copyright (C) 2026 Intel Corporation
> + */
> +
> +#define pr_fmt(fmt) KBUILD_MODNAME ": tdx_connect: " fmt
> +
> +#include <linux/pci.h>
> +#include <linux/pci-tsm.h>
> +#include <linux/tsm.h>
> +#include <asm/tdx.h>
> +
> +#include "tdx-guest.h"
> +
> +struct tdx_devsec {
> + struct pci_tsm_devsec pci;
> +};
> +
> +static struct tdx_devsec *to_tdx_devsec(struct pci_tsm *tsm)
> +{
> + return container_of(tsm, struct tdx_devsec, pci.base_tsm);
> +}
> +
> +static struct pci_tsm *tdx_devsec_lock(struct tsm_dev *tsm_dev, struct pci_dev *pdev)
> +{
> + int ret;
> +
> + struct tdx_devsec *tdevsec __free(kfree) = kzalloc(sizeof(*tdevsec), GFP_KERNEL);
> + if (!tdevsec)
> + return ERR_PTR(-ENOMEM);
> +
> + ret = pci_tsm_devsec_constructor(pdev, &tdevsec->pci, tsm_dev);
> + if (ret)
> + return ERR_PTR(ret);
> +
> + return &no_free_ptr(tdevsec)->pci.base_tsm;
> +}
> +
> +static void tdx_devsec_unlock(struct pci_tsm *tsm)
> +{
> + struct tdx_devsec *tdevsec = to_tdx_devsec(tsm);
> +
> + kfree(tdevsec);
> +}
> +
> +static int tdx_devsec_run(struct pci_dev *pdev)
> +{
> + return -EOPNOTSUPP;
> +}
> +
> +static struct pci_tsm_ops tdx_devsec_ops = {
> + .lock = tdx_devsec_lock,
> + .unlock = tdx_devsec_unlock,
> + .run = tdx_devsec_run,
> +};
> +
> +static void devsec_tsm_remove(void *tsm_dev)
> +{
> + tsm_unregister(tsm_dev);
> +}
> +
> +int tdx_connect_init(struct device *dev)
> +{
> + struct tsm_dev *tsm_dev;
> + u64 config, ret;
> +
> + ret = tdg_vm_rd(TDCS_CONFIG_FLAGS, &config);
> + if (ret)
> + return -EIO;
The kernel already manadates and assumes TDCS_CONFIG_FLAGS is always supported
in disable_sept_ve().
Can we make them consistent? Maybe just treat config as 0 when reading
TDCS_CONFIG_FLAGS fails?
> +
> + if (!(config & TDCS_CONFIG_TDX_CONNECT))
> + return 0;
> +
> + tsm_dev = tsm_register(dev, &tdx_devsec_ops);
> + if (IS_ERR(tsm_dev))
> + return PTR_ERR(tsm_dev);
> +
> + return devm_add_action_or_reset(dev, devsec_tsm_remove, tsm_dev);
> +}
> diff --git a/drivers/virt/coco/tdx-guest/tdx-guest.c b/drivers/virt/coco/tdx-guest/main.c
> similarity index 98%
> rename from drivers/virt/coco/tdx-guest/tdx-guest.c
> rename to drivers/virt/coco/tdx-guest/main.c
> index d0303e31e816..801a1f2b5f3d 100644
> --- a/drivers/virt/coco/tdx-guest/tdx-guest.c
> +++ b/drivers/virt/coco/tdx-guest/main.c
> @@ -25,6 +25,8 @@
> #include <asm/cpu_device_id.h>
> #include <asm/tdx.h>
>
> +#include "tdx-guest.h"
> +
> /* TDREPORT buffer */
> static u8 *tdx_report_buf;
>
> @@ -428,6 +430,10 @@ static int __init tdx_guest_init(void)
> if (ret)
> goto free_quote;
>
> + ret = tdx_connect_init(tdx_misc_dev.this_device);
> + if (ret)
> + pr_warn("Failed to enable TDX Connect: %d\n", ret);
> +
> return 0;
>
> free_quote:
> diff --git a/drivers/virt/coco/tdx-guest/tdx-guest.h b/drivers/virt/coco/tdx-guest/tdx-guest.h
> new file mode 100644
> index 000000000000..4218541c7f3b
> --- /dev/null
> +++ b/drivers/virt/coco/tdx-guest/tdx-guest.h
> @@ -0,0 +1,20 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/*
> + * TDX guest driver private declarations
> + *
> + * Copyright (C) 2026 Intel Corporation
> + */
> +
> +#ifndef __TDX_GUEST_H
> +#define __TDX_GUEST_H
> +
> +#include <linux/kernel.h>
> +#include <linux/device.h>
> +
> +#ifdef CONFIG_TDX_CONNECT_GUEST
> +extern int tdx_connect_init(struct device *dev);
extern is not needed.
> +#else
> +static inline int tdx_connect_init(struct device *dev) { return 0; }
> +#endif /* CONFIG_TDX_CONNECT_GUEST */
> +
> +#endif /* __TDX_GUEST_H */
next prev parent reply other threads:[~2026-10-26 1:12 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 4:10 [RFC PATCH 00/15] PCI/TSM: coco/tdx-guest: Implement TDX-Connect PCIe TDISP (phase2) Zhenzhong Duan
2026-09-24 4:10 ` [RFC PATCH 01/15] x86/tdx: Export tdg_vm_rd() for tdx-guest module Zhenzhong Duan
2026-09-30 22:13 ` Peter Fang
2026-10-01 12:38 ` Xu Yilun
2026-10-08 6:45 ` Duan, Zhenzhong
2026-10-08 16:30 ` Edgecombe, Rick P
2026-09-24 4:10 ` [RFC PATCH 02/15] x86/tdx: Add TDCM hypercall wrapper for TDX Connect Zhenzhong Duan
2026-10-13 14:34 ` Nikolay Borisov
2026-10-14 6:19 ` Duan, Zhenzhong
2026-10-14 6:27 ` Nikolay Borisov
2026-10-14 7:22 ` Duan, Zhenzhong
2026-10-26 0:33 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 03/15] x86/tdx: Add TDG.TDI.RD module call " Zhenzhong Duan
2026-09-25 0:06 ` Edgecombe, Rick P
2026-10-08 6:27 ` Duan, Zhenzhong
2026-10-08 16:42 ` Edgecombe, Rick P
2026-10-09 2:28 ` Duan, Zhenzhong
2026-10-26 0:51 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 04/15] virt: tdx-guest: Support devsec TSM for secure devices Zhenzhong Duan
2026-10-15 13:42 ` Xu Yilun
2026-10-16 6:42 ` Duan, Zhenzhong
2026-10-26 1:12 ` Xiaoyao Li [this message]
2026-09-24 4:10 ` [RFC PATCH 05/15] virt: tdx-guest: Add TDCM helpers and TEE-IO support check Zhenzhong Duan
2026-10-13 14:31 ` Nikolay Borisov
2026-10-14 6:11 ` Duan, Zhenzhong
2026-10-26 1:26 ` Xiaoyao Li
2026-10-26 7:13 ` Nikolay Borisov
2026-10-14 12:52 ` Nikolay Borisov
2026-10-15 6:24 ` Duan, Zhenzhong
2026-10-26 2:06 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 06/15] virt: tdx-guest: Support TDI bind and unbind operations Zhenzhong Duan
2026-10-13 12:10 ` Nikolay Borisov
2026-10-14 3:06 ` Duan, Zhenzhong
2026-10-14 6:32 ` Nikolay Borisov
2026-10-14 7:33 ` Duan, Zhenzhong
2026-10-17 18:38 ` Nikolay Borisov
2026-10-19 2:16 ` Duan, Zhenzhong
2026-10-26 2:32 ` Xiaoyao Li
2026-10-26 2:38 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 07/15] PCI/TSM: Track Device Interface Report MMIO range index Zhenzhong Duan
2026-10-26 2:45 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 08/15] x86/tdx: Add TDG.MMIO.ACCEPT module call wrapper for TDX Connect Zhenzhong Duan
2026-09-24 23:41 ` Edgecombe, Rick P
2026-09-25 0:02 ` Edgecombe, Rick P
2026-10-08 6:01 ` Duan, Zhenzhong
2026-10-08 16:47 ` Edgecombe, Rick P
2026-10-08 5:49 ` Duan, Zhenzhong
2026-10-08 16:44 ` Edgecombe, Rick P
2026-10-09 2:16 ` Duan, Zhenzhong
2026-09-24 4:10 ` [RFC PATCH 09/15] virt: tdx-guest: Capture the TDI report during device lock Zhenzhong Duan
2026-10-26 5:04 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 10/15] virt: tdx-guest: Set up and accept private MMIO ranges Zhenzhong Duan
2026-10-26 5:22 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 11/15] x86/tdx: Add TDG.TDI.START module call wrapper for TDX Connect Zhenzhong Duan
2026-09-24 4:10 ` [RFC PATCH 12/15] virt: tdx-guest: Support Trust Device Interface (TDI) activation Zhenzhong Duan
2026-10-26 7:19 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 13/15] x86/tdx: Add __tdcall_saved() helper Zhenzhong Duan
2026-10-26 7:35 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 14/15] x86/tdx: Add TDG.DMAR.ACCEPT module call wrapper for TDX Connect Zhenzhong Duan
2026-10-26 7:39 ` Xiaoyao Li
2026-09-24 4:10 ` [RFC PATCH 15/15] virt: tdx-guest: Accept default DMAR entry during PCI driver attach Zhenzhong Duan
2026-10-26 7:49 ` Xiaoyao Li
2026-10-26 12:02 ` Jason Gunthorpe
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=59b997ce-f5b9-4a3b-9de8-91533289bfe7@intel.com \
--to=xiaoyao.li@intel.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgg@nvidia.com \
--cc=kas@kernel.org \
--cc=kevin.tian@intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nicolinc@nvidia.com \
--cc=pbonzini@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@kernel.org \
--cc=vishal.l.verma@intel.com \
--cc=x86@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®