From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org
Cc: alison.schofield@intel.com
Subject: [NDCTL PATCH v3 0/3] ndctl: Add support and test for CXL Features support
Date: Fri, 7 Feb 2025 16:46:32 -0700 [thread overview]
Message-ID: <20250207234718.2387622-1-dave.jiang@intel.com> (raw)
v3:
- Update test to use opcode instead of command id.
v2:
- Drop features device enumeration
- Add discovery of char device under memdev
The series provides support of libcxl enumerating FWCTL character device
under the cxl_memdev device. It discovers the char device major
and minor numbers for the CXL features device in order to allow issuing
of ioctls to the device.
A unit test is added to locate cxl_memdev exported by the cxl_test
kernel module and issue all the supported ioctls to the associated
FWCTL char device to verify that all the ioctl paths are working as expected.
Kernel series: https://lore.kernel.org/linux-cxl/20250207233914.2375110-1-dave.jiang@intel.com/T/#t
Dave Jiang (3):
cxl: Add cxl_bus_get_by_provider()
cxl: Enumerate major/minor of FWCTL char device
cxl/test: Add test for cxl features device
cxl/lib/libcxl.c | 85 +++++++++++++++++
cxl/lib/libcxl.sym | 7 ++
cxl/lib/private.h | 1 +
cxl/libcxl.h | 4 +
test/cxl-features.sh | 19 ++++
test/fwctl.c | 364 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
test/meson.build | 17 ++++
7 files changed, 497 insertions(+)
next reply other threads:[~2025-02-07 23:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 23:46 Dave Jiang [this message]
2025-02-07 23:46 ` [NDCTL PATCH v3 1/3] cxl: Add cxl_bus_get_by_provider() Dave Jiang
2025-02-07 23:46 ` [NDCTL PATCH v3 2/3] cxl: Enumerate major/minor of FWCTL char device Dave Jiang
2025-02-07 23:46 ` [NDCTL PATCH v3 3/3] cxl/test: Add test for cxl features device Dave Jiang
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=20250207234718.2387622-1-dave.jiang@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=linux-cxl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox