linux-kernel - Re: [PATCH v16 3/4] PCI/DOE: Expose the DOE features via sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250305194156.GA309932@bhelgaas>
Date: Wed, 5 Mar 2025 13:41:56 -0600
From: Bjorn Helgaas <helgaas@...nel.org>
To: Alistair Francis <alistair@...stair23.me>
Cc: bhelgaas@...gle.com, linux-pci@...r.kernel.org,
	Jonathan.Cameron@...wei.com, lukas@...ner.de,
	alex.williamson@...hat.com, christian.koenig@....com,
	kch@...dia.com, gregkh@...uxfoundation.org, logang@...tatee.com,
	linux-kernel@...r.kernel.org, alistair23@...il.com,
	chaitanyak@...dia.com, rdunlap@...radead.org
Subject: Re: [PATCH v16 3/4] PCI/DOE: Expose the DOE features via sysfs

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@...r.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?