From: Alison Schofield <alison.schofield@intel.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [NDCTL PATCH v6 4/4] cxl/test: Add test for cxl features device
Date: Thu, 15 May 2025 11:24:35 -0700 [thread overview]
Message-ID: <aCYxY8tmvJ14sWB-@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250509164006.687873-5-dave.jiang@intel.com>
On Fri, May 09, 2025 at 09:39:15AM -0700, Dave Jiang wrote:
> Add a unit test to verify the features ioctl commands. Test support added
> for locating a features device, retrieve and verify the supported features
> commands, retrieve specific feature command data, retrieve test feature
> data, and write and verify test feature data.
>
> Acked-by: Dan Williams <dan.j.williams@intel.com>
> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
> ---
> v6:
> - Provide a fwctl option and move everything behind it. (Dan)
> - Rename test app back to fwctl.c. (Dan)
> - Fix spelling error. (Dan)
> - Expand scope of fwctl device in documentation. (Dan)
> ---
> cxl/fwctl/cxl.h | 2 +-
> meson_options.txt | 2 +
> test/cxl-features.sh | 31 +++
> test/fwctl.c | 439 +++++++++++++++++++++++++++++++++++++++++++
> test/meson.build | 19 ++
> 5 files changed, 492 insertions(+), 1 deletion(-)
> create mode 100755 test/cxl-features.sh
> create mode 100644 test/fwctl.c
>
skip -
> diff --git a/test/meson.build b/test/meson.build
> index d871e28e17ce..918db7e6049b 100644
> --- a/test/meson.build
> +++ b/test/meson.build
> @@ -17,6 +17,13 @@ ndctl_deps = libndctl_deps + [
> versiondep,
> ]
>
> +libcxl_deps = [
> + cxl_dep,
> + ndctl_dep,
> + uuid,
> + kmod,
> +]
> +
> libndctl = executable('libndctl', testcore + [ 'libndctl.c'],
> dependencies : libndctl_deps,
> include_directories : root_inc,
> @@ -235,6 +242,18 @@ if get_option('keyutils').enabled()
> ]
> endif
>
> +uuid_dep = dependency('uuid', required: false)
> +if get_option('fwctl').enabled() and uuid_dep.found()
> + fwctl = executable('fwctl', 'fwctl.c',
> + dependencies : libcxl_deps,
> + include_directories : root_inc,
> + )
> + cxl_features = find_program('cxl-features.sh')
> + tests += [
> + [ 'cxl-features.sh', cxl_features, 'cxl' ],
> + ]
> +endif
Is the fwctl feature enabled fuss still needed now that the UAPI headers
are vendored locally? Seems the test will quickly SKIP if fwctl dev not
found. I kind of like the idea of seeing a 'SKIP' and knowing the test
didn't run than seeing nothing at all in the test output.
> +
> foreach t : tests
> test(t[0], t[1],
> is_parallel : false,
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-05-15 18:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 16:39 [NDCTL PATCH v6 0/4] ndctl: Add support and test for CXL Features support Dave Jiang
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 [this message]
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=aCYxY8tmvJ14sWB-@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox