From: Helge Deller <deller@gmx.de>
To: Guenter Roeck <linux@roeck-us.net>, Yury Norov <yury.norov@gmail.com>
Cc: James.Bottomley@hansenpartnership.com,
linux-parisc@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-kernel@vger.kernel.org
Subject: Re: Kunit test failures with cpumask tests on parisc
Date: Mon, 5 Feb 2024 10:28:27 +0100 [thread overview]
Message-ID: <929506cf-a1a7-436e-938d-4e5eff0181e4@gmx.de> (raw)
In-Reply-To: <e6f0ab85-5bbe-41c1-8976-5ba00044998c@roeck-us.net>
On 2/5/24 07:53, Guenter Roeck wrote:
> when running cpumask Kunit tests on parisc/parisc64 in qemu,
> I get the following errors.
>
> KTAP version 1
> # Subtest: cpumask
> # module: cpumask_kunit
> 1..6
> # test_cpumask_weight: EXPECTATION FAILED at lib/cpumask_kunit.c:68
> Expected nr_cpu_ids == cpumask_weight(((const struct cpumask *)&__cpu_possible_mask)), but
> nr_cpu_ids == 16 (0x10)
> cpumask_weight(((const struct cpumask *)&__cpu_possible_mask)) == 1 (0x1)
> cpu_possible_mask contains CPUs 0
> not ok 1 test_cpumask_weight
> # test_cpumask_first: EXPECTATION FAILED at lib/cpumask_kunit.c:79
> Expected nr_cpu_ids <= cpumask_first_zero(((const struct cpumask *)&__cpu_possible_mask)), but
> nr_cpu_ids == 16 (0x10)
> cpumask_first_zero(((const struct cpumask *)&__cpu_possible_mask)) == 1 (0x1)
> cpu_possible_mask contains CPUs 0
> not ok 2 test_cpumask_first
> # test_cpumask_last: EXPECTATION FAILED at lib/cpumask_kunit.c:87
> Expected nr_cpu_ids - 1 == cpumask_last(((const struct cpumask *)&__cpu_possible_mask)), but
> nr_cpu_ids - 1 == 15 (0xf)
> cpumask_last(((const struct cpumask *)&__cpu_possible_mask)) == 0 (0x0)
> cpu_possible_mask contains CPUs 0
> not ok 3 test_cpumask_last
> # test_cpumask_next: EXPECTATION FAILED at lib/cpumask_kunit.c:94
> Expected nr_cpu_ids <= cpumask_next_zero(-1, ((const struct cpumask *)&__cpu_possible_mask)), but
> nr_cpu_ids == 16 (0x10)
> cpumask_next_zero(-1, ((const struct cpumask *)&__cpu_possible_mask)) == 1 (0x1)
> cpu_possible_mask contains CPUs 0
> not ok 4 test_cpumask_next
> ok 5 test_cpumask_iterators
> ok 6 test_cpumask_iterators_builtin
> # cpumask: pass:2 fail:4 skip:0 total:6
> # Totals: pass:2 fail:4 skip:0 total:6
> not ok 5 cpumask
>
> It appears that parisc sets __cpu_possible_mask to the number of online CPUs,
> which is limited in qemu and doesn't match CONFIG_NR_CPUS. Is this a problem
> with the unit test or with the parisc architecture, or does the unit test
> simply not apply for parisc ?
Thank you for finding and reporting this!
It's a bug (or a misunderstanding) in the parisc kernel.
Reverting commit 0921244f6f4f ("parisc: Only list existing CPUs in cpu_possible_mask")
fixes the KUnit test.
Furthermore the revert fixes the issue that CPU hot-unplugging doesn't
work and which I just was starting to debug:
https://lore.kernel.org/lkml/Zb0mbHlIud_bqftx@slm.duckdns.org/t/
Helge
next prev parent reply other threads:[~2024-02-05 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 6:53 Guenter Roeck
2024-02-05 9:28 ` Helge Deller [this message]
2024-02-05 16:06 ` Guenter Roeck
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=929506cf-a1a7-436e-938d-4e5eff0181e4@gmx.de \
--to=deller@gmx.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=yury.norov@gmail.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
all inboxes | Powered by JetHome®