Linux CXL
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Marc Herbert <Marc.Herbert@linux.intel.com>,
	Alison Schofield <alison.schofield@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, 22 May 2025 10:46:45 -0700	[thread overview]
Message-ID: <fc21a089-efa0-41b4-bc3e-70f6e7423719@intel.com> (raw)
In-Reply-To: <ee7865a2-d57a-4b94-820f-7a3be90377b9@linux.intel.com>



On 5/22/25 10:37 AM, Marc Herbert wrote:
> On 2025-05-15 11:28, Dave Jiang wrote:
> 
>>>>  
>>>> +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.
>>
>> This gives the option to disable fwctl if needed. Also there is a libuuid dependency since we use uuid lib calls. 
> 
> Is it possible to go anywhere without uuid?
> 
> fedora$ sudo dnf remove libuuid-devel
>         meson setup build
> 
> ...
> Run-time dependency libkmod found: YES 33
> Run-time dependency libudev found: YES 256
> Found CMake: /usr/bin/cmake (3.30.8)
> Run-time dependency uuid found: NO (tried pkgconfig and cmake)
> 
> meson.build:144:0: ERROR: Dependency "uuid" not found, tried pkgconfig and cmake
> 
> 
> meson setup --help | grep uuid  # empty
> git grep get_option.*uuid       # empty
> grep -C 5 uuid meson.build      # does not look optional
> 
> It looks like a hard requirement to me.
> 
> UUIDs are rarely ever "optional". It could be required only
> by some optional tool but that does not seem to be the case here

Apparently it's not an requirement for kernel build. As my feature user header caused issues due to lack of libuuid package.

> 
> Fun fact: it's not even possible to remove /usr/include/uuid/uuid.h
> on Arch Linux, not without breaking the system.
> 
> 


  reply	other threads:[~2025-05-22 17:47 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
2025-05-15 18:28     ` Dave Jiang
2025-05-22 17:37       ` Marc Herbert
2025-05-22 17:46         ` Dave Jiang [this message]
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=fc21a089-efa0-41b4-bc3e-70f6e7423719@intel.com \
    --to=dave.jiang@intel.com \
    --cc=Marc.Herbert@linux.intel.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@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