From: Marc Zyngier <maz@kernel.org>
To: "Colton Lewis" <coltonlewis@google.com>
Cc: kvmarm@lists.linux.dev, "Oliver Upton" <oupton@kernel.org>,
sashiko-reviews@lists.linux.dev
Subject: Re: [PATCH] irqchip/gic-v4: Use a separate lockdep class for vPE doorbell IRQs
Date: Sun, 25 Oct 2026 10:13:21 +0000 [thread overview]
Message-ID: <868q3mytoe.wl-maz@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-183282@kernel.org>
On Fri, 23 Oct 2026 23:16:32 +0100,
sashiko-bot@kernel.org wrote:
>
> Should vPE doorbell IRQs also be marked with IRQ_NOTHREAD (or requested with
> IRQF_NO_THREAD) so they are never force-threaded?
This seems legit. Colton?
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-25 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 21:52 [PATCH] irqchip/gic-v4: Use a separate lockdep class for vPE doorbell IRQs Colton Lewis
2026-10-23 22:16 ` sashiko-bot
2026-10-25 10:13 ` Marc Zyngier [this message]
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=868q3mytoe.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=coltonlewis@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=oupton@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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