From: Li Zhijian <lizhijian@fujitsu.com>
To: nvdimm@lists.linux.dev
Cc: linux-cxl@vger.kernel.org, dave.jiang@intel.com,
Li Zhijian <lizhijian@fujitsu.com>
Subject: [ndctl PATCH v2 2/2] README.md: document CXL unit tests
Date: Wed, 31 May 2023 10:24:14 +0800 [thread overview]
Message-ID: <20230531022414.7604-2-lizhijian@fujitsu.com> (raw)
In-Reply-To: <20230531022414.7604-1-lizhijian@fujitsu.com>
It requires some CLX specific kconfigs and testing purpose module
Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
---
V2: Add separate CXL unit test entry # Dave
---
README.md | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/README.md b/README.md
index 7c7cf0dd065d..4874430a023b 100644
--- a/README.md
+++ b/README.md
@@ -82,6 +82,32 @@ loaded. To build and install nfit_test.ko:
sudo make modules_install
```
+1. CXL test
+
+ The unit tests will also run CXL test by default. In order to make the
+ CXL test work smoothly, we need to install the cxl_test.ko as well.
+
+ Obtain the CXL kernel source(optional). For example,
+ `git clone -b pending git://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git`
+
+ Enable CXL specific kernel configurations
+ ```
+ CONFIG_CXL_BUS=m
+ CONFIG_CXL_PCI=m
+ CONFIG_CXL_ACPI=m
+ CONFIG_CXL_PMEM=m
+ CONFIG_CXL_MEM=m
+ CONFIG_CXL_PORT=m
+ CONFIG_CXL_REGION=y
+ CONFIG_CXL_REGION_INVALIDATION_TEST=y
+ CONFIG_DEV_DAX_CXL=m
+ ```
+ Install cxl_test.ko
+ ```
+ make M=tools/testing/cxl
+ sudo make M=tools/testing/cxl modules_install
+ sudo make modules_install
+ ```
1. Now run `meson test -C build` in the ndctl source directory, or `ndctl test`,
if ndctl was built with `-Dtest=enabled` as a configuration option to meson.
--
2.29.2
prev parent reply other threads:[~2023-05-31 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 2:24 [ndctl PATCH v2 1/2] CONTRIBUTING.md: document cxl mailing list Li Zhijian
2023-05-31 2:24 ` Li Zhijian [this message]
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=20230531022414.7604-2-lizhijian@fujitsu.com \
--to=lizhijian@fujitsu.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 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.