From: Guenter Roeck <linux@roeck-us.net>
To: Brian Norris <briannorris@chromium.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Tsai Sung-Fu <danielsftsai@google.com>,
Douglas Anderson <dianders@chromium.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] genirq: Add kunit tests for depth counts
Date: Fri, 15 Aug 2025 17:24:24 -0700 [thread overview]
Message-ID: <fc42ed34-e87d-4868-94bb-30554a3f6ec4@roeck-us.net> (raw)
In-Reply-To: <aJ91RRsMB-duD2yR@google.com>
On 8/15/25 10:58, Brian Norris wrote:
> On Sun, Aug 10, 2025 at 12:37:31PM -0700, Guenter Roeck wrote:
>> The new code calls irq_domain_alloc_descs(), making it dependent
>> on IRQ_DOMAIN. However, specifying that dependency directly is not
>> possible:
>>
>> config IRQ_KUNIT_TEST
>> bool "KUnit tests for IRQ management APIs" if !KUNIT_ALL_TESTS
>> depends on KUNIT=y
>> + depends on IRQ_DOMAIN
>> default KUNIT_ALL_TESTS
>> imply SMP
>> help
>>
>> results in:
>>
>> *** Default configuration is based on 'defconfig'
>> error: recursive dependency detected!
>> symbol SMP is implied by IRQ_KUNIT_TEST
>> symbol IRQ_KUNIT_TEST depends on IRQ_DOMAIN
>> symbol IRQ_DOMAIN is selected by IRQ_DOMAIN_HIERARCHY
>> symbol IRQ_DOMAIN_HIERARCHY is selected by GENERIC_IRQ_IPI
>> symbol GENERIC_IRQ_IPI depends on SMP
>>
>> This is seen with alpha configurations such as alpha:defconfig after
>> adding the IRQ_DOMAIN dependency.
>>
>> I have no idea how to resolve this. For now I disabled IRQ_KUNIT_TEST
>> for my alpha test builds.
>
> How about 'select'? That's the usual way IRQ_DOMAIN is managed anyway.
>
> It builds for me, but my distro doesn't provide an Alpha QEMU, so I
> can't test it.
>
I can try, but the irq test code fails for me all over the place, so I am
not sure if it is worth it.
From my current upstream test results (6.17-rc1):
Build results:
total: 162 pass: 162 fail: 0
Qemu test results:
total: 637 pass: 637 fail: 0
Unit test results:
pass: 640017 fail: 649
The failures are all from the irq test code. I didn't have time to analyze it.
You can find details at https://kerneltests.org/builders in the "master" column
if you have time.
Note that "imply SMP" does not make SMP mandatory. I can still disable it after
enabling IRQ_KUNIT_TEST on x86. Frankly I don't really understand what "imply"
is supposed to be useful for.
Guenter
> --- a/kernel/irq/Kconfig
> +++ b/kernel/irq/Kconfig
> @@ -148,6 +148,7 @@ config IRQ_KUNIT_TEST
> bool "KUnit tests for IRQ management APIs" if !KUNIT_ALL_TESTS
> depends on KUNIT=y
> default KUNIT_ALL_TESTS
> + select IRQ_DOMAIN
> imply SMP
> help
> This option enables KUnit tests for the IRQ subsystem API. These are
next prev parent reply other threads:[~2025-08-16 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 21:08 Brian Norris
2025-06-13 13:34 ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-05 17:45 ` [PATCH v4] " Guenter Roeck
2025-08-05 18:32 ` [PATCH] genirq/test: Resolve irq lock inversion warnings Brian Norris
2025-08-05 19:54 ` Guenter Roeck
2025-08-06 8:33 ` [tip: irq/urgent] " tip-bot2 for Brian Norris
2025-08-10 19:37 ` [PATCH v4] genirq: Add kunit tests for depth counts Guenter Roeck
2025-08-15 17:58 ` Brian Norris
2025-08-16 0:24 ` Guenter Roeck [this message]
2025-08-16 2:23 ` Brian Norris
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=fc42ed34-e87d-4868-94bb-30554a3f6ec4@roeck-us.net \
--to=linux@roeck-us.net \
--cc=briannorris@chromium.org \
--cc=danielsftsai@google.com \
--cc=dianders@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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®