All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev
Cc: alison.schofield@intel.com
Subject: [NDCTL PATCH v6 0/4] ndctl: Add support and test for CXL Features support
Date: Fri,  9 May 2025 09:39:11 -0700	[thread overview]
Message-ID: <20250509164006.687873-1-dave.jiang@intel.com> (raw)

v6:
- Rename cxl-features.control.c back to fwctl.c. (Dan)
- Move features behind a meson option. (Dan)
- See individual commits for specific changes from v5.

v5:
- Add documentation for exported symbols. (Alison)
- Create 'struct cxl_fwctl' as object under cxl_memdev. (Dan)
- Make command prep common code. (Alison)
- Rename fwctl.c to cxl-features-control.c. (Alison)
- See individual commits for specific changes from v4.

v4:
- Adjust to kernel changes of input/output structs
- Fixup skip/pass/fail logic
- Added new kernel headers detection and dependency in meson.build

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 (4):
      cxl: Add cxl_bus_get_by_provider()
      cxl: Enumerate major/minor of FWCTL char device
      ndctl: Add features.h from kernel UAPI
      cxl/test: Add test for cxl features device

 Documentation/cxl/lib/libcxl.txt |  24 ++++
 cxl/fwctl/cxl.h                  |  56 ++++++++
 cxl/fwctl/features.h             | 179 ++++++++++++++++++++++++
 cxl/fwctl/fwctl.h                | 141 +++++++++++++++++++
 cxl/lib/libcxl.c                 |  90 ++++++++++++
 cxl/lib/libcxl.sym               |   8 ++
 cxl/lib/private.h                |   6 +
 cxl/libcxl.h                     |   7 +
 meson_options.txt                |   2 +
 test/cxl-features.sh             |  31 +++++
 test/fwctl.c                     | 439 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 test/meson.build                 |  19 +++
 12 files changed, 1002 insertions(+)


             reply	other threads:[~2025-05-09 16:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 16:39 Dave Jiang [this message]
2025-05-09 16:39 ` [NDCTL PATCH v6 1/4] cxl: Add cxl_bus_get_by_provider() Dave Jiang
2025-05-09 16:39 ` [NDCTL PATCH v6 2/4] cxl: Enumerate major/minor of FWCTL char device Dave Jiang
2025-05-09 16:39 ` [NDCTL PATCH v6 3/4] ndctl: Add features.h from kernel UAPI Dave Jiang
2025-05-09 16:39 ` [NDCTL PATCH v6 4/4] cxl/test: Add test for cxl features device Dave Jiang
2025-05-15 18:24   ` Alison Schofield
2025-05-15 18:28     ` Dave Jiang
2025-05-22 17:37       ` Marc Herbert
2025-05-22 17:46         ` Dave Jiang
2025-05-22 18:25           ` Marc Herbert

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=20250509164006.687873-1-dave.jiang@intel.com \
    --to=dave.jiang@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    /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.