Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: <marc.herbert@linux.intel.com>
Cc: <linux-cxl@vger.kernel.org>, <nvdimm@lists.linux.dev>,
	<dan.j.williams@intel.com>
Subject: Re: [ndctl PATCH 1/2] README.md: add CONFIG_s missing to pass NFIT tests
Date: Wed, 21 May 2025 21:47:18 -0700	[thread overview]
Message-ID: <aC6sVpma71y4jH7S@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250521002640.1700283-1-marc.herbert@linux.intel.com>

On Wed, May 21, 2025 at 12:26:39AM +0000, marc.herbert@linux.intel.com wrote:
> From: Marc Herbert <marc.herbert@linux.intel.com>
> 
> Found by trial and error. As of kernel v6.15, the CONFIG_s in this
> version are enough to give to ./scripts/kconfig/merge_config.sh and pass
> `meson test --suite=ndctl:ndctl` and `meson test --suite=ndctl:dax`
> 
> This has been manually tested with only `make defconfig ARCH=x86_64` as
> a starting point. This is admittedly incomplete test coverage but still
> a massively better starting point for other ARCHs and a big time
> saver. There's a good chance it's enough for other ARCHs too.

Thanks for doing this Marc! 

I'm wondering about the need to delineate between what is needed to load
and use the cxl-test or nfit-test modules as opposed to what is required to
run all the unit tests.

I believe my environment, and yours, and most other folks using these
environments are doing so in a VM so it's no big deal to load up all the
things.

Maybe just a gentle separator in the list showing required and optional.
I would NOT go so far as to pick apart which ones are needed for which
test because that is a slippery slope. If a user is in test running mode
they need all the things.

> 
> Link: https://lore.kernel.org/nvdimm/aed71134-1029-4b88-ab20-8dfa527a7438@linux.intel.com/
> Signed-off-by: Marc Herbert <marc.herbert@linux.intel.com>
> ---
>  README.md | 10 ++++++++++
>  1 file changed, 10 insertions(+)
> 
> diff --git a/README.md b/README.md
> index db25a9114402..a37991ccefa2 100644
> --- a/README.md
> +++ b/README.md
> @@ -69,10 +69,20 @@ loaded.  To build and install nfit_test.ko:
>     CONFIG_NVDIMM_PFN=y
>     CONFIG_NVDIMM_DAX=y
>     CONFIG_DEV_DAX_PMEM=m
> +   CONFIG_FS_DAX=y
> +   CONFIG_XFS_FS=y
> +   CONFIG_DAX=m
> +   CONFIG_DEV_DAX=m
>     CONFIG_ENCRYPTED_KEYS=y
>     CONFIG_NVDIMM_SECURITY_TEST=y
>     CONFIG_STRICT_DEVMEM=y
>     CONFIG_IO_STRICT_DEVMEM=y
> +   CONFIG_ACPI_NFIT=m
> +   CONFIG_NFIT_SECURITY_DEBUG=y
> +   CONFIG_MEMORY_FAILURE=y
> +   CONFIG_MEMORY_HOTPLUG=y
> +   CONFIG_MEMORY_HOTREMOVE=y
> +   CONFIG_TRANSPARENT_HUGEPAGE=y
>     ```
>  
>  1. Build and install the unit test enabled libnvdimm modules in the
> -- 
> 2.49.0
> 

  parent reply	other threads:[~2025-05-22  4:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-21  0:26 [ndctl PATCH 1/2] README.md: add CONFIG_s missing to pass NFIT tests marc.herbert
2025-05-21  0:26 ` [ndctl PATCH 2/2] README.md: add CONFIG_s missing to pass CXL tests marc.herbert
2025-05-22  4:47 ` Alison Schofield [this message]
2025-05-22 14:47   ` [ndctl PATCH 1/2] README.md: add CONFIG_s missing to pass NFIT tests Marc Herbert
2025-05-29  2:44     ` Alison Schofield

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=aC6sVpma71y4jH7S@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=marc.herbert@linux.intel.com \
    --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