mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Florian Fainelli <florian.fainelli@broadcom.com>
To: linux-kernel@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
	Kieran Bingham <kbingham@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Shanker Donthineni <sdonthineni@nvidia.com>
Subject: Re: [PATCH] scripts/gdb: Fix interrupts.py after maple tree conversion
Date: Fri, 20 Jun 2025 11:26:15 -0700	[thread overview]
Message-ID: <8ad1c722-62ad-48f6-80b2-8f07b2e84bae@broadcom.com> (raw)
In-Reply-To: <20250620181446.477246-1-florian.fainelli@broadcom.com>

On 6/20/25 11:14, Florian Fainelli wrote:
> In commit 721255b9826b ("genirq: Use a maple tree for interrupt
> descriptor management"), the irq_desc_tree was replaced with a
> sparse_irqs tree using a maple tree structure. In the interest of
> providing both a minimal bugfix as well as something that is unlikely to
> break in the future, invoke the irq_to_desc() function directly from
> within GDB in order to obtain the interrupt number. This requires us to
> handle the gdb.error exception to continue walking the tree.
 > > Fixes: 721255b9826b ("genirq: Use a maple tree for interrupt 
descriptor management")
> Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>

Humm, looks like we might not have a choice than to be able to parse a 
maple tree within GDB. While this approach of calling irq_to_desc() 
worked correctly on x86 under QEMU, this failed on arm64.

pw-bot: cr
-- 
Florian

      reply	other threads:[~2025-06-20 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 18:14 Florian Fainelli
2025-06-20 18:26 ` Florian Fainelli [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=8ad1c722-62ad-48f6-80b2-8f07b2e84bae@broadcom.com \
    --to=florian.fainelli@broadcom.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kbingham@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sdonthineni@nvidia.com \
    --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®