From: Yi Sun <yi.sun@intel.com>
To: dave.jiang@intel.com, vinicius.gomes@intel.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
fenghuay@nvidia.com, philip.lantz@intel.com
Cc: yi.sun@intel.com, gordon.jin@intel.com, anil.s.keshavamurthy@intel.com
Subject: [PATCH v2 0/2] dmaengine: idxd: Add basic DSA 3.0 capability and SGL support
Date: Fri, 20 Jun 2025 21:09:51 +0800 [thread overview]
Message-ID: <20250620130953.1943703-1-yi.sun@intel.com> (raw)
This patch series introduces foundational support for DSA 3.0 features,
exposing hardware capability registers to userspace in the IDXD driver.
DSA 3.0 introduces several new features that require awareness and
configuration from both kernel and userspace. It is necessary to
understand the hardware's capabilities for userspace tools (e.g.,
idxd-config, libraries, and applications) to make use of the features
properly, such as supported features, memory layouts, and opcode
compatibility.
Patch 1/2 exposes the three new capability registers (dsacap0-2)
introduced in the DSA 3.0 specification through a new sysfs entry.
This allows tools and users to query hardware capabilities such as
supported SGL formats, floating-point options, and maximum supported
sizes.
Patch 2/2 enables configuration of the maximum SGL size for DSA 3.0
devices. Some DSA 3.0 opcodes (e.g., Gather Copy, Gather Reduce) require
that the workqueue's SGL size is explicitly configured. This patch sets
that value based on hardware capabilities at initialization time,
allowing these opcodes to function without additional user configuration.
---
Changes in v2:
- Added the link to the DSA 3.0 spec in the commit message (Dave)
- Fixed typos in the commit messages (Fenghua)
- Updated the sysfs ABI documentation for accuracy (Fenghua)
- Renamed the ABI entry from 'dsacap' to 'dsacaps' (Fenghua, Philip)
- Moved the definition of dsacap0_reg from patch #2 to patch #1 (Fenghua)
- Fixed the output format (Fenghua, Philip)
- Reordered the capability registers to match the DSA 3.0 spec (Fenghua)
- Add conditon checking to avoid accessing dsacaps when DSA 3.0 is not
supported (Fenghua)
Yi Sun (2):
dmaengine: idxd: Expose DSA3.0 capabilities through sysfs
dmaengine: idxd: Add Max SGL Size Support for DSA3.0
.../ABI/stable/sysfs-driver-dma-idxd | 15 ++++++++++
drivers/dma/idxd/device.c | 5 ++++
drivers/dma/idxd/idxd.h | 19 +++++++++++++
drivers/dma/idxd/init.c | 11 ++++++++
drivers/dma/idxd/registers.h | 28 ++++++++++++++++++-
drivers/dma/idxd/sysfs.c | 24 ++++++++++++++++
6 files changed, 101 insertions(+), 1 deletion(-)
--
2.43.0
next reply other threads:[~2025-06-20 13:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 13:09 Yi Sun [this message]
2025-06-20 13:09 ` [PATCH v2 1/2] dmaengine: idxd: Expose DSA3.0 capabilities through sysfs Yi Sun
2025-06-24 0:40 ` Vinicius Costa Gomes
2025-06-20 13:09 ` [PATCH v2 2/2] dmaengine: idxd: Add Max SGL Size Support for DSA3.0 Yi Sun
2025-06-24 0:41 ` Vinicius Costa Gomes
2025-08-12 2:11 ` Yi Sun
2025-08-20 17:30 ` Vinod Koul
2025-08-21 4:36 ` Sun, Yi
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=20250620130953.1943703-1-yi.sun@intel.com \
--to=yi.sun@intel.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=fenghuay@nvidia.com \
--cc=gordon.jin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philip.lantz@intel.com \
--cc=vinicius.gomes@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