All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Thomas Gleixner <tglx@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <clrkwllms@kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] irqchip/gic-v3-its: Don't acquire rt_spin_lock in allocate_vpe_l1_table()
Date: Tue, 10 Mar 2026 08:12:05 +0000	[thread overview]
Message-ID: <86fr686r3e.wl-maz@kernel.org> (raw)
In-Reply-To: <0a332e19-c99e-4dc5-a2d0-b36a2aef80a1@redhat.com>

On Mon, 09 Mar 2026 19:06:04 +0000,
Waiman Long <longman@redhat.com> wrote:
> 
> On 1/21/26 10:49 PM, Waiman Long wrote:
> > 
> > On 1/21/26 3:41 PM, Waiman Long wrote:
> >> 
> >>>> Waiman, can you please give the following hack a go on your box? The
> >>>> machines I have are thankfully limited to a single ITS group, so I
> >>>> can't directly reproduce your issue.
> >>> Have you managed to try this hack? I may be able to spend some time
> >>> addressing the issue in the next cycle if I have an indication that
> >>> I'm on the right track.
> >> 
> >> Yes, I have tried out your hack patch and the 2-socket Grace test
> >> system booted up without producing any bug report for a RT debug
> >> kernel. I will try out your official patch once it come out. So
> >> moving the memory allocation to a later part of the hotplug bringup
> >> pipeline where sleeping is allowed should work. 
> > 
> > Attaching the dmesg log for your further investigation. 
> 
> Ping,
> 
> Are you planning to send out an official patch soon?

Soon? On a geological scale, certainly. On a more practical scale,
when I get time, which hasn't happened so far in this cycle ($WORK
gets, unsurprisingly, in the way of solving problems I don't have).

If that's not soon enough, feel free to expand the hack I posted to
include all boot-time tables.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


  reply	other threads:[~2026-03-10  8:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 21:53 [PATCH] irqchip/gic-v3-its: Don't acquire rt_spin_lock in allocate_vpe_l1_table() Waiman Long
2026-01-08  8:26 ` Marc Zyngier
2026-01-08 22:11   ` Thomas Gleixner
2026-01-09 16:13     ` Marc Zyngier
2026-01-11  9:39       ` Thomas Gleixner
2026-01-11 10:38         ` Marc Zyngier
2026-01-11 16:20           ` Thomas Gleixner
2026-01-12 11:20             ` Marc Zyngier
2026-01-12 14:08               ` Sebastian Andrzej Siewior
2026-01-12 14:38                 ` Marc Zyngier
2026-01-21  8:38               ` Marc Zyngier
2026-01-21 16:48                 ` Waiman Long
2026-01-21 20:41                 ` Waiman Long
2026-01-22  3:49                   ` Waiman Long
2026-03-09 19:06                     ` Waiman Long
2026-03-10  8:12                       ` Marc Zyngier [this message]
2026-01-11 23:02           ` Waiman Long
2026-01-12 15:09             ` Thomas Gleixner
2026-01-12 17:14               ` Waiman Long
2026-01-13 11:55                 ` Sebastian Andrzej Siewior
2026-01-13 23:25                   ` Alexei Starovoitov
2026-01-14 16:01                     ` Sebastian Andrzej Siewior
2026-01-14 17:59                   ` Vlastimil Babka
2026-01-21 16:37                     ` Waiman Long
2026-01-10 21:47   ` Waiman Long

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=86fr686r3e.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=longman@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.