From: Dave Jiang <dave.jiang@intel.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: linux-cxl@vger.kernel.org, djbw@kernel.org, dave@stgolabs.net,
jic23@kernel.org, vishal.l.verma@intel.com
Subject: Re: [PATCH v7 1/7] cxl/test: Add test for module parameters
Date: Tue, 30 Jun 2026 10:28:18 -0700 [thread overview]
Message-ID: <04ba8663-ca6a-4f6f-8e53-432ddfa887d0@intel.com> (raw)
In-Reply-To: <akP7C0oFiqxxi6fK@aschofie-mobl2.lan>
On 6/30/26 10:21 AM, Alison Schofield wrote:
> On Mon, Jun 29, 2026 at 03:10:58PM -0700, Dave Jiang wrote:
>> Add a test for module paraters during module init to make sure that
>> only one is activated.
>>
>> Suggested-by: Alison Schofield <alison.schofield@intel.com>
>> Signed-off-by: Dave Jiang <dave.jiang@intel.com>
>> ---
>> tools/testing/cxl/test/cxl.c | 20 ++++++++++++++++++++
>> tools/testing/cxl/test/hmem_test.c | 3 ++-
>> tools/testing/cxl/test/mock.h | 2 ++
>> 3 files changed, 24 insertions(+), 1 deletion(-)
>>
>> diff --git a/tools/testing/cxl/test/cxl.c b/tools/testing/cxl/test/cxl.c
>> index ef92dd35e030..198a128181b9 100644
>> --- a/tools/testing/cxl/test/cxl.c
>> +++ b/tools/testing/cxl/test/cxl.c
>> @@ -1827,11 +1827,31 @@ static struct attribute *cxl_acpi_attrs[] = {
>> };
>> ATTRIBUTE_GROUPS(cxl_acpi);
>>
>> +static bool __init have_multiple_modparms(void)
>> +{
>> + int count = 0;
>> +
>> + if (interleave_arithmetic)
>> + count++;
>> + if (extended_linear_cache)
>> + count++;
>> + if (fail_autoassemble)
>> + count++;
>> + if (hmem_test)
>> + count++;
>> +
>> + return count > 1;
>> +}
>
> fail_autoassemble is a modifier of hmem_test, not a standalone mode.
> Needs to be dropped from above func for cxl-dax-hmem.sh to run.
>
> Tested with this diff:
> --- a/tools/testing/cxl/test/cxl.c
> +++ b/tools/testing/cxl/test/cxl.c
> @@ -2081,8 +2081,6 @@ static bool __init have_multiple_modparms(void)
> count++;
> if (extended_linear_cache)
> count++;
> - if (fail_autoassemble)
> - count++;
> if (hmem_test)
> count++;
> if (type2_test)
>
ok will drop
next prev parent reply other threads:[~2026-06-30 17:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-29 22:10 [PATCH v7 0/7] cxl: Add CXL type2 accelerator support for cxl_test Dave Jiang
2026-06-29 22:10 ` [PATCH v7 1/7] cxl/test: Add test for module parameters Dave Jiang
2026-06-29 22:21 ` sashiko-bot
2026-06-30 17:21 ` Alison Schofield
2026-06-30 17:28 ` Dave Jiang [this message]
2026-06-29 22:10 ` [PATCH v7 2/7] cxl/test: Add type2 support for mock CFMWS0 Dave Jiang
2026-06-29 22:11 ` [PATCH v7 3/7] cxl/test: Refactor platform device enumerations Dave Jiang
2026-06-29 22:11 ` [PATCH v7 4/7] cxl/test: Add hierarchy enumeration support for type2 device Dave Jiang
2026-07-01 7:31 ` Li Ming
2026-07-01 14:53 ` Dave Jiang
2026-06-29 22:11 ` [PATCH v7 5/7] cxl/test: Propagate -ENOMEM on platform_device_alloc() failures Dave Jiang
2026-06-29 22:11 ` [PATCH v7 6/7] cxl/test: Fixup hdm init for auto region to support type2 Dave Jiang
2026-06-29 22:11 ` [PATCH v7 7/7] cxl/test: Add cxl_test accelerator driver Dave Jiang
2026-06-29 22:23 ` sashiko-bot
2026-06-30 17:23 ` [PATCH v7 0/7] cxl: Add CXL type2 accelerator support for cxl_test Alison Schofield
2026-06-30 20:50 ` 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=04ba8663-ca6a-4f6f-8e53-432ddfa887d0@intel.com \
--to=dave.jiang@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox