From: Marc Zyngier <maz@kernel•org>
To: Waiman Long <longman@redhat•com>
Cc: Thomas Gleixner <tglx@linutronix•de>,
Sebastian Andrzej Siewior <bigeasy@linutronix•de>,
Clark Williams <clrkwllms@kernel•org>,
Steven Rostedt <rostedt@goodmis•org>,
Andrew Morton <akpm@linux-foundation•org>,
David Hildenbrand <david@kernel•org>,
Lorenzo Stoakes <ljs@kernel•org>,
"Liam R. Howlett" <liam@infradead•org>,
Vlastimil Babka <vbabka@kernel•org>,
Mike Rapoport <rppt@kernel•org>,
Suren Baghdasaryan <surenb@google•com>,
Michal Hocko <mhocko@suse•com>,
linux-arm-kernel@lists•infradead.org,
linux-kernel@vger•kernel.org, linux-mm@kvack•org,
linux-rt-devel@lists•linux.dev
Subject: Re: [PATCH 2/2] irqchip/gic-v3-its: Use GFP_ATOMIC_RT gfp flag in allocate_vpe_l1_table()
Date: Fri, 22 May 2026 09:17:35 +0100 [thread overview]
Message-ID: <861pf3x3hc.wl-maz@kernel.org> (raw)
In-Reply-To: <20260520204628.933654-2-longman@redhat.com>
On Wed, 20 May 2026 21:46:28 +0100,
Waiman Long <longman@redhat•com> wrote:
>
> A longer term solution is to defer the allocation to a later stage of the
> hotplug pipeline where interrupt isn't disabled.
And that's what needs doing. Not papering over this in a bizarre way.
I proposed a potential solution a few months back, but didn't get a
chance to work on it. If you have the bandwidth, that's the way to go.
But papering over this issue this way seems like a bad case of short
term and unsustainable hack.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2026-05-22 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 20:46 [PATCH 1/2] gfp_types: Introduce a new GFP_ATOMIC_RT gfp flag Waiman Long
2026-05-20 20:46 ` [PATCH 2/2] irqchip/gic-v3-its: Use GFP_ATOMIC_RT gfp flag in allocate_vpe_l1_table() Waiman Long
2026-05-22 8:17 ` Marc Zyngier [this message]
2026-05-22 9:06 ` Lorenzo Stoakes
2026-05-21 16:40 ` [PATCH 1/2] gfp_types: Introduce a new GFP_ATOMIC_RT gfp flag Lorenzo Stoakes
2026-05-21 17:40 ` Waiman Long
2026-05-22 8:46 ` Lorenzo Stoakes
2026-05-25 8:41 ` Michal Hocko
2026-05-26 8:28 ` Sebastian Andrzej Siewior
2026-05-26 13:55 ` Vlastimil Babka (SUSE)
2026-05-27 8:41 ` Michal Hocko
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=861pf3x3hc.wl-maz@kernel.org \
--to=maz@kernel$(echo .)org \
--cc=akpm@linux-foundation$(echo .)org \
--cc=bigeasy@linutronix$(echo .)de \
--cc=clrkwllms@kernel$(echo .)org \
--cc=david@kernel$(echo .)org \
--cc=liam@infradead$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mm@kvack$(echo .)org \
--cc=linux-rt-devel@lists$(echo .)linux.dev \
--cc=ljs@kernel$(echo .)org \
--cc=longman@redhat$(echo .)com \
--cc=mhocko@suse$(echo .)com \
--cc=rostedt@goodmis$(echo .)org \
--cc=rppt@kernel$(echo .)org \
--cc=surenb@google$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
--cc=vbabka@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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