linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Norris <briannorris@chromium.org>
To: David Gow <davidgow@google.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	kunit-dev@googlegroups.com
Subject: Re: [PATCH v2 4/6] genirq/test: Depend on SPARSE_IRQ
Date: Mon, 25 Aug 2025 14:23:11 -0700	[thread overview]
Message-ID: <aKzUP8TczQmuAEXU@google.com> (raw)
In-Reply-To: <CABVgOSngoD0fh1WEkUCEwSdk0Joypo3dA_Y_SjW+K=nVDnZs3Q@mail.gmail.com>

On Sat, Aug 23, 2025 at 02:59:26PM +0800, David Gow wrote:
> On Sat, 23 Aug 2025 at 03:01, Brian Norris <briannorris@chromium.org> wrote:
> > Notably, this also excludes ARCH=um from running any of these tests,
> > even though some of them might work.
> 
> I confess to being disappointed that we lose ARCH=um support with this
> -- it's nice to have it run on the "default" configuration -- but the
> correct way of solving this is probably to support SPARSE_IRQ on UML,
> which is probably more work than it's worth.

I made an educated guess on how to support SPARSE_IRQ for ARCH=um, and I
got something working here:

[PATCH] um: Support SPARSE_IRQ
http://lore.kernel.org/all/20250825212031.111027-1-briannorris@chromium.org

Brian

  reply	other threads:[~2025-08-25 21:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-22 18:59 [PATCH v2 0/6] genirq/test: Platform/architecture fixes Brian Norris
2025-08-22 18:59 ` [PATCH v2 1/6] genirq/test: Select IRQ_DOMAIN Brian Norris
2025-08-23  1:13   ` Guenter Roeck
2025-09-03 15:12   ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-22 18:59 ` [PATCH v2 2/6] genirq/test: Factor out fake-virq setup Brian Norris
2025-08-23  1:13   ` Guenter Roeck
2025-09-03 15:12   ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-22 18:59 ` [PATCH v2 3/6] genirq/test: Fail early if we can't request an IRQ Brian Norris
2025-08-23  1:13   ` Guenter Roeck
2025-09-03 15:12   ` [tip: irq/core] genirq/test: Fail early if interrupt request fails tip-bot2 for Brian Norris
2025-08-22 18:59 ` [PATCH v2 4/6] genirq/test: Depend on SPARSE_IRQ Brian Norris
2025-08-23  1:13   ` Guenter Roeck
2025-08-23  6:59   ` David Gow
2025-08-25 21:23     ` Brian Norris [this message]
2025-09-03 15:12   ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-22 18:59 ` [PATCH v2 5/6] genirq/test: Drop CONFIG_GENERIC_IRQ_MIGRATION assumptions Brian Norris
2025-08-23  1:13   ` Guenter Roeck
2025-09-03 15:12   ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-22 18:59 ` [PATCH v2 6/6] genirq/test: Ensure CPU 1 is online for hotplug test Brian Norris
2025-08-23  1:14   ` Guenter Roeck
2025-09-03 15:12   ` [tip: irq/core] " tip-bot2 for Brian Norris
2025-08-22 23:26 ` [PATCH v2 0/6] genirq/test: Platform/architecture fixes Guenter Roeck
2025-08-23  1:15 ` 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=aKzUP8TczQmuAEXU@google.com \
    --to=briannorris@chromium.org \
    --cc=davidgow@google.com \
    --cc=geert@linux-m68k.org \
    --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;
as well as URLs for NNTP newsgroup(s).