All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Brian van der Beek <bbeek@marvell.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	Christophe Therene <ctherene@marvell.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>
Subject: Re: Question on DOE requirements for CXL/CDAT and CMA/SPDM
Date: Fri, 24 Feb 2023 07:56:29 +0100	[thread overview]
Message-ID: <20230224065629.GA15827@wunner.de> (raw)
In-Reply-To: <SJ0PR18MB496423534AC55973B92E3913B3AB9@SJ0PR18MB4964.namprd18.prod.outlook.com>

On Thu, Feb 23, 2023 at 01:06:47PM +0000, Brian van der Beek wrote:
> For a CXL device that support both CMA/SPDM and CXL Table Access DOE
> (CDAT) data objects, is it mandatory to have a dedicated DOE instance
> for the CMA/SPMA protocol data objects?

Yes, that follows from the requirements you quoted from the PCIe spec.


> Or is it permitted for the CMA/SPDM and CXL protocols to share a
> single DOE instance?

You'd violate the PCIe spec and depend on software to handle such
non-standard behavior gracefully.


> I am reaching out to you, as I am hoping you could provide some
> insight on the Linux CMA/SPDM implementation and whether it allows
> for a DOE instance to be shared with CXL/CDAT data objects.

The code as it currently is will allow that.


> PCI-SIG replied that the requirement of a dedicated DOE instance for
> CMA/SPDM was an intentional choice based on the idea that the software
> attached to the DOE instances would be different.

The PCISIG has published the DOE 1.1 ECN in the meantime and it
allows for concurrent use of a mailbox by different software
entities (kernel, BIOS, ...) through the use of a unique
Connection ID.  You could ask the PCISIG to revisit the spec's
protocol restriction for CMA/SPDM in light of DOE 1.1.
There's an ECR for CMA/SPDM currently under development.

Thanks,

Lukas

      parent reply	other threads:[~2023-02-24  6:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SJ0PR18MB496423534AC55973B92E3913B3AB9@SJ0PR18MB4964.namprd18.prod.outlook.com>
2023-02-23 14:00 ` Question on DOE requirements for CXL/CDAT and CMA/SPDM Jonathan Cameron
2023-02-24  6:56 ` Lukas Wunner [this message]

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=20230224065629.GA15827@wunner.de \
    --to=lukas@wunner.de \
    --cc=bbeek@marvell.com \
    --cc=ctherene@marvell.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /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.