All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Anisa Su <anisa.su887@gmail.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
	Jonathan Cameron <jic23@kernel.org>,
	Dave Jiang <dave.jiang@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <iweiny@kernel.org>, Li Ming <ming.li@zohomail.com>,
	Richard Cheng <icheng@nvidia.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 1/4] Documentation/driver-api/cxl: Add a testing page
Date: Mon, 19 Oct 2026 13:39:11 -0700	[thread overview]
Message-ID: <atZ_75-jlBACRvb0@aschofie-mobl2.lan> (raw)
In-Reply-To: <atKqrRww5GlgzRlA@cxlqual>

On Sat, Oct 17, 2026 at 07:52:29AM +0900, Anisa Su wrote:
> On Tue, Oct 13, 2026 at 09:17:52PM -0700, Alison Schofield wrote:
> > The CXL documentation does not describe the subsystem's testing
> > infrastructure or provide guidance on choosing between cxl_test
> > and KUnit.
> > 
> > Add a testing page that describes when to use each framework, how
> > to run the tests, and how to add a CXL KUnit test.
> > 
> > Suggested-by: Dave Jiang <dave.jiang@intel.com>
> > Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> > ---
> >  Documentation/driver-api/cxl/index.rst   |   1 +
> >  Documentation/driver-api/cxl/testing.rst | 117 +++++++++++++++++++++++
> >  2 files changed, 118 insertions(+)

snip

> > +KUnit
> > +=====
> > +
> > +KUnit tests run self-contained logic in the kernel without any CXL topology.
> > +KUnit is suited to logic that can be exercised with controlled test inputs,
> > +including encode/decode helpers, address translation and interleave calculations,
> > +parsers of device- or firmware-supplied data, and mailbox command handling
> > +through a stub transport.
> > +
> > +To run all of the CXL KUnit tests, from the top of the kernel tree::
> > +
> > +  ./tools/testing/kunit/kunit.py run --kunitconfig=drivers/cxl
> > +
> > +This builds a test kernel in .kunit/ using drivers/cxl/.kunitconfig and runs it
> > +under User Mode Linux (UML). The running kernel is not modified, and no
> > +installation is required. The test kernel runs the tests, reports the results,
> > +and exits.
> > +
> > +Add --arch=x86_64 to run the tests under QEMU instead.
> > +
> Add --arch=<arch> ...
> Maybe also point at "--arch=help"
> 
> Reviewed-by: Anisa Su <anisa.su@samsung.com>

Thanks for the review Anisa.

I have this prep'd for v2:

-Add --arch=x86_64 to run the tests under QEMU instead.
+Use --arch=<arch> to run the tests under QEMU instead.
+Use --arch=help to list supported architectures.

-- Alison


  reply	other threads:[~2026-10-19 20:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-14  4:17 [PATCH 0/4] cxl: Add KUnit tests and documentation Alison Schofield
2026-10-14  4:17 ` [PATCH 1/4] Documentation/driver-api/cxl: Add a testing page Alison Schofield
2026-10-14 21:34   ` Alison Schofield
2026-10-16 19:02     ` Jonathan Cameron
2026-10-16 19:01   ` Jonathan Cameron
2026-10-19 20:44     ` Alison Schofield
2026-10-16 22:52   ` Anisa Su
2026-10-19 20:39     ` Alison Schofield [this message]
2026-10-14  4:17 ` [PATCH 2/4] cxl: Add KUnit tests for HDM decoder encoding helpers Alison Schofield
2026-10-15  9:16   ` Li Ming
2026-10-16 20:01   ` Jonathan Cameron
2026-10-19 21:09     ` Alison Schofield
2026-10-14  4:17 ` [PATCH 3/4] cxl/mbox: Treat unknown device return codes as errors Alison Schofield
2026-10-14 15:06   ` 黄高彬
2026-10-15  9:22   ` Li Ming
2026-10-19 21:01     ` Alison Schofield
2026-10-20  2:35       ` Li Ming
2026-10-16 20:03   ` Jonathan Cameron
2026-10-14  4:17 ` [PATCH 4/4] cxl/mbox: Add KUnit tests for cxl_internal_send_cmd() Alison Schofield
2026-10-15  9:37   ` Li Ming
2026-10-19 21:22     ` Alison Schofield
2026-10-20  2:34       ` Li Ming
2026-10-14 20:52 ` [PATCH 0/4] cxl: Add KUnit tests and documentation Dave Jiang

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=atZ_75-jlBACRvb0@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=anisa.su887@gmail.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=icheng@nvidia.com \
    --cc=iweiny@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=ming.li@zohomail.com \
    --cc=vishal.l.verma@intel.com \
    /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.