From: Bjorn Helgaas <helgaas@kernel.org>
To: Alistair Francis <alistair@alistair23.me>
Cc: bhelgaas@google.com, linux-pci@vger.kernel.org,
Jonathan.Cameron@huawei.com, lukas@wunner.de,
alex.williamson@redhat.com, christian.koenig@amd.com,
kch@nvidia.com, gregkh@linuxfoundation.org, logang@deltatee.com,
linux-kernel@vger.kernel.org, alistair23@gmail.com,
chaitanyak@nvidia.com, rdunlap@infradead.org
Subject: Re: [PATCH v16 3/4] PCI/DOE: Expose the DOE features via sysfs
Date: Wed, 5 Mar 2025 13:41:56 -0600 [thread overview]
Message-ID: <20250305194156.GA309932@bhelgaas> (raw)
In-Reply-To: <20250227043404.2452562-3-alistair@alistair23.me>
On Thu, Feb 27, 2025 at 02:34:02PM +1000, Alistair Francis wrote:
> The PCIe 6 specification added support for the Data Object
> Exchange (DOE).
> When DOE is supported the DOE Discovery Feature must be implemented per
> PCIe r6.1 sec 6.30.1.1. The protocol allows a requester to obtain
> information about the other DOE features supported by the device.
> +What: /sys/bus/pci/devices/.../doe_features
> +Date: March 2025
> +Contact: Linux PCI developers <linux-pci@vger.kernel.org>
> +Description:
> + This directory contains a list of the supported
> + Data Object Exchange (DOE) features. The features are
> + the file name. The contents of each file is the raw vendor id and
> + data object feature values.
> +
> + The value comes from the device and specifies the vendor and
> + data object type supported. The lower (RHS of the colon) is
> + the data object type in hex. The upper (LHS of the colon)
> + is the vendor ID.
> +
> + As all DOE devices must support the DOE discovery protocol, if
> + DOE is supported you will at least see the doe_discovery file, with
> + this contents
> +
> + # cat doe_features/doe_discovery
> + 0001:00
> +
> + If the device supports other protocols you will see other files
> + as well. For example is CMA/SPDM and secure CMA/SPDM are supported
> + the doe_features directory will look like this
> +
> + # ls doe_features
> + 0001:01 0001:02 doe_discovery
Does this text need to be updated with s/protocol/feature/ as in the
first patch?
next prev parent reply other threads:[~2025-03-05 19:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 4:34 [PATCH v16 1/4] PCI/DOE: Rename DOE protocol to feature Alistair Francis
2025-02-27 4:34 ` [PATCH v16 2/4] PCI/DOE: Rename Discovery Response Data Object Contents to type Alistair Francis
2025-02-27 4:34 ` [PATCH v16 3/4] PCI/DOE: Expose the DOE features via sysfs Alistair Francis
2025-03-05 19:41 ` Bjorn Helgaas [this message]
2025-03-05 20:05 ` Bjorn Helgaas
2025-03-06 7:28 ` Alistair Francis
2025-02-27 4:34 ` [PATCH v16 4/4] PCI/DOE: Allow enabling DOE without CXL Alistair Francis
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=20250305194156.GA309932@bhelgaas \
--to=helgaas@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=bhelgaas@google.com \
--cc=chaitanyak@nvidia.com \
--cc=christian.koenig@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=kch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=lukas@wunner.de \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox