mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: David Gow <davidgow@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Guenter Roeck <linux@roeck-us.net>,
	linux-kernel@vger.kernel.org, kunit-dev@googlegroups.com
Subject: Re: [PATCH 0/6] genirq/test: Platform/architecture fixes
Date: Wed, 20 Aug 2025 10:22:29 -0700	[thread overview]
Message-ID: <aKYEVTRhzbXvwlbD@google.com> (raw)
In-Reply-To: <CABVgOSkUT_yYqBvk2-+OozKEBybj-07mcRAVECNYQiw+1P67eA@mail.gmail.com>

On Wed, Aug 20, 2025 at 03:00:34PM +0800, David Gow wrote:
> Looks like __irq_alloc_descs() is returning -ENOMEM (as
> irq_find_free_area() is returning 200 w/ nr_irqs == 200, and
> CONFIG_SPARSE_IRQ=n).

Thanks for the insight. I bothered compiling my own qemu just so I can
run m68k this time, and I can reproduce.

I wonder if I should make everything (CONFIG_IRQ_KUNIT_TEST) depend on
CONFIG_SPARSE_IRQ, since it seems like arches like m68k can't enable
SPARSE_IRQ, and they can't allocate new (fake) IRQs without it. That'd
be a tweak to patch 4.

Or maybe just 'depends on !M68K', since architectures with higher
NR_IRQS headroom may still work even without SPARSE_IRQ.

> But all of the other architectures I found worked okay, so this is at
> least an improvement.

Thanks for the testing.

Brian

  reply	other threads:[~2025-08-20 17:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 19:27 Brian Norris
2025-08-18 19:27 ` [PATCH 1/6] genirq/test: Select IRQ_DOMAIN Brian Norris
2025-08-18 19:27 ` [PATCH 2/6] genirq/test: Factor out fake-virq setup Brian Norris
2025-08-18 19:27 ` [PATCH 3/6] genirq/test: Fail early if we can't request an IRQ Brian Norris
2025-08-18 19:27 ` [PATCH 4/6] genirq/test: Skip managed-affinity tests with !SPARSE_IRQ Brian Norris
2025-08-18 19:27 ` [PATCH 5/6] genirq/test: Drop CONFIG_GENERIC_IRQ_MIGRATION assumptions Brian Norris
2025-08-18 19:27 ` [PATCH 6/6] genirq/test: Ensure CPU 1 is online for hotplug test Brian Norris
2025-08-20  7:00 ` [PATCH 0/6] genirq/test: Platform/architecture fixes David Gow
2025-08-20 17:22   ` Brian Norris [this message]
2025-08-20 21:37     ` Guenter Roeck
2025-08-21  3:45     ` David Gow
2025-08-21  7:05       ` Geert Uytterhoeven
2025-08-21 15:32         ` Brian Norris
2025-08-21 17:02 ` Guenter Roeck
2025-08-21 19:06   ` Brian Norris
2025-08-22 18:34     ` Guenter Roeck
2025-08-22 19:01       ` 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=aKYEVTRhzbXvwlbD@google.com \
    --to=briannorris@chromium.org \
    --cc=davidgow@google.com \
    --cc=kunit-dev@googlegroups.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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®