The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Boqun Feng <boqun@kernel.org>
To: Kuan-Wei Chiu <visitorckw@gmail.com>
Cc: tglx@kernel.org, peterz@infradead.org, lyude@redhat.com,
	radu@rendec.net, jserv@ccns.ncku.edu.tw, marscheng@google.com,
	eleanor15x@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] irq: Make refcount_interrupt kunit test selectable
Date: Sun, 23 Aug 2026 14:10:01 -0700	[thread overview]
Message-ID: <aothqS6_4v-kvque@tardis.local> (raw)
In-Reply-To: <20260823171721.3059733-1-visitorckw@gmail.com>

On Sun, Aug 23, 2026 at 05:17:21PM +0000, Kuan-Wei Chiu wrote:
> Currently, refcount_interrupt_test is built unconditionally when
> CONFIG_KUNIT is enabled, causing it to run unexpectedly during boot.
> 
> Fix this by introducing CONFIG_REFCOUNT_INTERRUPT_KUNIT_TEST so the
> test can be configured independently, following standard kunit
> practices.
> 

Sorry about this..

> Fixes: 07a88e2bcd5b ("irq: Add KUnit test for refcounted interrupt enable/disable")
> Signed-off-by: Kuan-Wei Chiu <visitorckw@gmail.com>

Reviewed-by: Boqun Feng <boqun@kernel.org>

Regards,
Boqun

> ---
>  kernel/irq/Kconfig  | 12 ++++++++++++
>  kernel/irq/Makefile |  2 +-
>  2 files changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/irq/Kconfig b/kernel/irq/Kconfig
> index 05cba4e16dad..6923f37eaab4 100644
> --- a/kernel/irq/Kconfig
> +++ b/kernel/irq/Kconfig
> @@ -150,6 +150,18 @@ config IRQ_KUNIT_TEST
>  
>  	  If unsure, say N.
>  
> +config REFCOUNT_INTERRUPT_KUNIT_TEST
> +	tristate "Test refcounted interrupt enable/disable" if !KUNIT_ALL_TESTS
> +	depends on KUNIT
> +	default KUNIT_ALL_TESTS
> +	help
> +	  This builds the kunit tests for the refcounted interrupt
> +	  infrastructure. It verifies the correctness of single, nested,
> +	  and multiple interrupt enable/disable state changes and ensures
> +	  that the underlying reference counting mechanisms work as expected.
> +
> +	  If unsure, say N.
> +
>  endmenu
>  
>  config GENERIC_IRQ_MULTI_HANDLER
> diff --git a/kernel/irq/Makefile b/kernel/irq/Makefile
> index 44c4d6fc502a..0e5df962a149 100644
> --- a/kernel/irq/Makefile
> +++ b/kernel/irq/Makefile
> @@ -16,4 +16,4 @@ obj-$(CONFIG_SMP) += affinity.o
>  obj-$(CONFIG_GENERIC_IRQ_DEBUGFS) += debugfs.o
>  obj-$(CONFIG_GENERIC_IRQ_MATRIX_ALLOCATOR) += matrix.o
>  obj-$(CONFIG_IRQ_KUNIT_TEST) += irq_test.o
> -obj-$(CONFIG_KUNIT) += refcount_interrupt_test.o
> +obj-$(CONFIG_REFCOUNT_INTERRUPT_KUNIT_TEST) += refcount_interrupt_test.o
> -- 
> 2.55.0.766.g2966f0265a-goog
> 

  parent reply	other threads:[~2026-08-23 21:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23 17:17 [PATCH] irq: Make refcount_interrupt kunit test selectable Kuan-Wei Chiu
2026-08-23 20:46 ` Radu Rendec
2026-08-23 21:08   ` Boqun Feng
2026-08-23 21:52     ` Radu Rendec
2026-08-24  5:23       ` Boqun Feng
2026-08-24 15:02         ` Radu Rendec
2026-08-25 14:09           ` Boqun Feng
2026-08-23 21:10 ` Boqun Feng [this message]
2026-08-24 15:14 ` Radu Rendec
2026-08-25 20:11 ` lyude

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=aothqS6_4v-kvque@tardis.local \
    --to=boqun@kernel.org \
    --cc=eleanor15x@gmail.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lyude@redhat.com \
    --cc=marscheng@google.com \
    --cc=peterz@infradead.org \
    --cc=radu@rendec.net \
    --cc=tglx@kernel.org \
    --cc=visitorckw@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