From: Kameron Carr <kameroncarr@linux.microsoft.com>
To: "Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>,
linux-coco@lists.linux.dev, kvmarm@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Alexey Kardashevskiy <aik@amd.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Jonathan Cameron <jic23@kernel.org>,
Marc Zyngier <maz@kernel.org>, Samuel Ortiz <sameo@rivosinc.com>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Will Deacon <will@kernel.org>,
Xu Yilun <yilun.xu@linux.intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: Re: [RFC PATCH v4 09/11] coco: guest: arm64: Hook TSM accept to Realm TDISP RUN transition
Date: Mon, 24 Aug 2026 15:28:19 -0700 [thread overview]
Message-ID: <f086f940-edaa-4bd5-ba11-e52e61fd6cee@linux.microsoft.com> (raw)
In-Reply-To: <20260427082805.931832-10-aneesh.kumar@kernel.org>
On 4/27/2026 1:28 AM, Aneesh Kumar K.V (Arm) wrote:
> Add an accept callback in pci_tsm_ops and implement cca_device_accept() to:
> - verify evidence generation (lock_nonce)
> - allocate and register protected MMIO ranges
> - transition TDI state to RUN
>
> Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
> Signed-off-by: Aneesh Kumar K.V (Arm) <aneesh.kumar@kernel.org>
> ---
> drivers/virt/coco/arm-cca-guest/arm-cca.c | 20 +++++++++++
> drivers/virt/coco/arm-cca-guest/rsi-da.c | 43 +++++++++++++++++++++++
> drivers/virt/coco/arm-cca-guest/rsi-da.h | 1 +
> 3 files changed, 64 insertions(+)
>
> diff --git a/drivers/virt/coco/arm-cca-guest/arm-cca.c b/drivers/virt/coco/arm-cca-guest/arm-cca.c
> index 320dd5aa7b9a..b29b3948a454 100644
> --- a/drivers/virt/coco/arm-cca-guest/arm-cca.c
> +++ b/drivers/virt/coco/arm-cca-guest/arm-cca.c
> @@ -499,9 +499,29 @@ static void cca_tsm_unlock(struct pci_tsm *tsm)
> kfree(cca_dsc);
> }
>
> +static int __cca_tsm_accept(struct pci_dev *pdev, unsigned long lock_nonce)
> +{
> + int ret;
> +
> + ret = cca_device_accept(pdev, lock_nonce);
> + if (ret) {
> + pci_err(pdev, "failed to transition the device to run state (%d)\n", ret);
> + return ret;
> + }
> + return 0;
> +}
> +
> +static int cca_tsm_accept(struct pci_dev *pdev)
> +{
> + struct cca_guest_dsc *dsc = to_cca_guest_dsc(pdev);
> +
> + return __cca_tsm_accept(pdev, dsc->dev_info.lock_nonce);
> +}
> +
> static struct pci_tsm_ops cca_devsec_pci_ops = {
> .lock = cca_tsm_lock,
> .unlock = cca_tsm_unlock,
> + .accept = cca_tsm_accept,
> };
>
> static void cca_devsec_tsm_remove(void *tsm_dev)
> diff --git a/drivers/virt/coco/arm-cca-guest/rsi-da.c b/drivers/virt/coco/arm-cca-guest/rsi-da.c
> index 039138768f8f..7c2b28fa43a1 100644
> --- a/drivers/virt/coco/arm-cca-guest/rsi-da.c
> +++ b/drivers/virt/coco/arm-cca-guest/rsi-da.c
> @@ -230,3 +230,46 @@ int cca_verify_digests(u64 hash_algo,
> }
> return 0;
> }
> +
> +int cca_device_accept(struct pci_dev *pdev, unsigned long lock_nonce)
> +{
> + int ret;
> + struct cca_guest_dsc *dsc = to_cca_guest_dsc(pdev);
> +
> + if (lock_nonce != dsc->dev_info.lock_nonce) {
> + pci_err(pdev, "Device evidence generation mismatch\n");
> + return -EIO;
> + }
> +
> + /* Allocation private mmio range based on interface report. */
> + struct pci_tsm_mmio *tsm_mmio __free(kfree) = pci_tsm_mmio_alloc(pdev);
> + if (!tsm_mmio) {
> + pci_err(pdev, "Protected mmio range allocation failure\n");
> + return -ENOMEM;
> + }
> +
> + /*
> + * Present the private mmio range in the resource hierarchy.
> + * We don't use this for ioremap, ioremap check the RIPAS value.
> + */
> + ret = pci_tsm_mmio_setup(pdev, tsm_mmio);
> + if (ret) {
> + pci_err(pdev, "Protected mmio setup failure\n");
> + return ret;
> + }
> +
> + ret = cca_map_evidence_report_range(pdev, tsm_mmio);
> + if (ret) {
> + pci_err(pdev, "failed to validate the interface report\n");
> + return ret;
> + }
> +
> + ret = rhi_vdev_set_tdi_state(pdev, RHI_DA_TDI_CONFIG_RUN);
> + if (ret) {
> + pci_err(pdev, "failed to switch the device (%u) to RUN state\n", ret);
> + return ret;
> + }
After calling pci_tsm_mmio_setup() we have mappings from insert_resource()
then failures from later return codes never call mmio_teardown() so
remove_resource() is never called, only kfree on the tsm_mmio.
Likewise after cca_map_evidence_report_range() the mmio entry memory ranges
have state RIPAS_DEV. Later failures never restore RIPAS_EMPTY.
Could clean up be handled better? Is there a reason these failures don't
have a rollback path?
Regards,
Kameron
> +
> + dsc->pci.mmio = no_free_ptr(tsm_mmio);
> + return 0;
> +}
> diff --git a/drivers/virt/coco/arm-cca-guest/rsi-da.h b/drivers/virt/coco/arm-cca-guest/rsi-da.h
> index 07a044d3e335..eeb049d374c5 100644
> --- a/drivers/virt/coco/arm-cca-guest/rsi-da.h
> +++ b/drivers/virt/coco/arm-cca-guest/rsi-da.h
> @@ -61,5 +61,6 @@ int cca_verify_digests(u64 hash_algo,
> uint8_t *interface_report, size_t interface_report_size,
> uint8_t *measurements, size_t measurements_size,
> struct rsi_vdevice_info *dev_info);
> +int cca_device_accept(struct pci_dev *pdev, unsigned long lock_nonce);
>
> #endif
next prev parent reply other threads:[~2026-08-24 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 8:27 [RFC PATCH v4 00/11] coco/TSM: Arm CCA guest TDISP lock/accept flow with verification and DMA enable Aneesh Kumar K.V (Arm)
2026-04-27 8:27 ` [RFC PATCH v4 01/11] coco: guest: arm64: Guest TSM callback and realm device lock support Aneesh Kumar K.V (Arm)
2026-04-27 8:27 ` [RFC PATCH v4 02/11] coco: guest: arm64: Fix a typo in the ARM_CCA_GUEST Kconfig help string ("and" -> "an") Aneesh Kumar K.V (Arm)
2026-04-27 8:27 ` [RFC PATCH v4 03/11] coco: guest: arm64: Add Realm Host Interface and guest DA helper Aneesh Kumar K.V (Arm)
2026-08-21 3:42 ` Kameron Carr
2026-04-27 8:27 ` [RFC PATCH v4 04/11] coco: guest: arm64: Support guest-initiated TDI lock/unlock transitions Aneesh Kumar K.V (Arm)
2026-04-27 8:27 ` [RFC PATCH v4 05/11] coco: guest: arm64: Refresh interface-report cache during device lock Aneesh Kumar K.V (Arm)
2026-04-27 8:28 ` [RFC PATCH v4 06/11] coco: guest: arm64: Add measurement refresh via RHI_DA_VDEV_GET_MEASUREMENTS Aneesh Kumar K.V (Arm)
2026-04-27 8:28 ` [RFC PATCH v4 07/11] coco: guest: arm64: Add guest APIs to read host-cached DA objects Aneesh Kumar K.V (Arm)
2026-08-18 17:43 ` Kameron Carr
2026-08-20 11:13 ` Aneesh Kumar K.V
2026-04-27 8:28 ` [RFC PATCH v4 08/11] coco: guest: arm64: Verify DA evidence with RSI_VDEV_GET_INFO digests Aneesh Kumar K.V (Arm)
2026-08-19 16:43 ` Kameron Carr
2026-08-20 11:18 ` Aneesh Kumar K.V
2026-04-27 8:28 ` [RFC PATCH v4 09/11] coco: guest: arm64: Hook TSM accept to Realm TDISP RUN transition Aneesh Kumar K.V (Arm)
2026-08-24 22:28 ` Kameron Carr [this message]
2026-08-25 4:47 ` Aneesh Kumar K.V
2026-04-27 8:28 ` [RFC PATCH v4 10/11] coco: arm64: dma: Update force_dma_unencrypted for accepted devices Aneesh Kumar K.V (Arm)
2026-04-27 8:28 ` [RFC PATCH v4 11/11] coco: guest: arm64: Enable vdev DMA after attestation Aneesh Kumar K.V (Arm)
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=f086f940-edaa-4bd5-ba11-e52e61fd6cee@linux.microsoft.com \
--to=kameroncarr@linux.microsoft.com \
--cc=Suzuki.Poulose@arm.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=jgg@ziepe.ca \
--cc=jic23@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=sameo@rivosinc.com \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
--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