From: Thomas Gleixner <tglx@kernel.org>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
Radu Rendec <radu@rendec.net>,
LKML <linux-kernel@vger.kernel.org>
Cc: x86@kernel.org, Dmitry Ilvokhin <d@ilvokhin.com>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>
Subject: Re: [patch v2 04/14] x86/irq: Make irqstats array based
Date: Fri, 27 Mar 2026 12:03:34 +0100 [thread overview]
Message-ID: <871ph5cz5l.ffs@tglx> (raw)
In-Reply-To: <5251d937-b737-48a0-8b14-ab375d28e341@broadcom.com>
Florian!
On Thu, Mar 26 2026 at 16:00, Florian Fainelli wrote:
> On 3/26/26 03:29, Thomas Gleixner wrote:
>> So if Radu hadn't noticed and pointed it out, I wouldn't have known
>> about it at all.
>
> Yes that's a fair point and it has been a complaint of mine whenever I
> had to use the GDB scripts because they get out of sync so easily with
> the code they are trying to parse, at some point it's not even fun.
>
> This should still apply if you want to take it:
>
> https://lore.kernel.org/all/20250625231053.1134589-6-florian.fainelli@broadcom.com/
That's just delegating something unenforcable, not automatically
testable to other maintainers. So it's not solving anything.
You want something which breaks the build for the submitter so that he
needs to go and fix up the gdb script or at least ask for help if he
can't figure it out on his own. If he does not build with debug enabled
the CI robots will catch it and send him back to the drawing board.
> As far as ensuring that the C/Rust code stays in sync with GDB at
> compile time, did not have any bright idea about how to do that.
Add parseable annotation into each of the snake scripts:
class kernel_dep(object):
def __init__(self, name, member=None, config=None, type=TYPE_VAR)
self.name = name
self.member = member
self.config = config
self.type = type
and per unit you add:
kernel_dependencies = [
kernel_dep(TYPE_VAR, 'nr_irqs'),
kernel_dep(TYPE_VAR, 'irq_stat', '__nmi_count', 'CONFIG_X86'),
kernel_dep('irq_chip', 'name', type=TYPE_STRUCT),
....
]
or something daft like that. I'm 100% sure that real snake experts will
come up with a way more elegant solution, but you get the idea.
Then have a script which collects this information from the source files
and validates it against the debug information in vmlinux. Obviously
this would allow you to validate the snake code against those
dependencies as well.
The first two entries would have caught both changes I made, the array
conversion of irq_stat and the rename of nr_irqs.
Hmm?
Thanks,
tglx
next prev parent reply other threads:[~2026-03-27 11:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 13:21 [patch v2 00/14] Improve /proc/interrupts further and add a binary interface Thomas Gleixner
2026-03-20 13:21 ` [patch v2 01/14] x86/irq: Optimize interrupts decimals printing Thomas Gleixner
2026-03-21 16:10 ` Radu Rendec
2026-03-20 13:21 ` [patch v2 02/14] genirq/proc: Avoid formatting zero counts in /proc/interrupts Thomas Gleixner
2026-03-21 16:38 ` Radu Rendec
2026-03-20 13:21 ` [patch v2 03/14] genirq/proc: Utilize irq_desc::tot_count to avoid evaluation Thomas Gleixner
2026-03-22 19:59 ` Radu Rendec
2026-03-20 13:21 ` [patch v2 04/14] x86/irq: Make irqstats array based Thomas Gleixner
2026-03-20 16:39 ` Michael Kelley
2026-03-21 16:38 ` Thomas Gleixner
2026-03-21 20:32 ` Michael Kelley
2026-03-23 19:24 ` Radu Rendec
2026-03-24 19:54 ` Thomas Gleixner
2026-03-24 20:21 ` Thomas Gleixner
2026-03-24 20:32 ` Radu Rendec
2026-03-25 19:20 ` Radu Rendec
2026-03-25 22:52 ` Thomas Gleixner
2026-03-25 22:54 ` Florian Fainelli
2026-03-26 10:29 ` Thomas Gleixner
2026-03-26 23:00 ` Florian Fainelli
2026-03-27 11:03 ` Thomas Gleixner [this message]
2026-03-26 12:34 ` Radu Rendec
2026-03-20 13:21 ` [patch v2 05/14] genirq: Expose nr_irqs in core code Thomas Gleixner
2026-03-23 19:48 ` Radu Rendec
2026-03-23 21:27 ` Thomas Gleixner
2026-03-20 13:21 ` [patch v2 06/14] genirq: Cache the condition for /proc/interrupts exposure Thomas Gleixner
2026-03-23 20:58 ` Radu Rendec
2026-03-24 20:31 ` Thomas Gleixner
2026-03-24 20:36 ` Radu Rendec
2026-03-20 13:21 ` [patch v2 07/14] genirq: Calculate precision only when required Thomas Gleixner
2026-03-25 19:47 ` Radu Rendec
2026-03-20 13:22 ` [patch v2 08/14] genirq: Add rcuref count to struct irq_desc Thomas Gleixner
2026-03-26 18:43 ` Dmitry Ilvokhin
2026-03-20 13:22 ` [patch v2 09/14] genirq: Expose irq_find_desc_at_or_after() in core code Thomas Gleixner
2026-03-26 19:13 ` Dmitry Ilvokhin
2026-03-26 21:11 ` Thomas Gleixner
2026-03-26 21:25 ` Thomas Gleixner
2026-03-20 13:22 ` [patch v2 10/14] genirq/proc: Speed up /proc/interrupts iteration Thomas Gleixner
2026-03-20 13:22 ` [patch v2 11/14] [RFC] genirq: Cache target CPU for single CPU affinities Thomas Gleixner
2026-03-20 13:22 ` [patch v2 12/14] [RFC] genirq/proc: Provide binary statistic interface Thomas Gleixner
2026-03-20 13:22 ` [patch v2 13/14] [RFC] genirq/proc: Provide architecture specific binary statistics Thomas Gleixner
2026-03-20 13:22 ` [patch v2 14/14] [RFC] x86/irq: Hook up architecture specific stats Thomas Gleixner
2026-03-20 16:45 ` [patch v2 00/14] Improve /proc/interrupts further and add a binary interface Michael Kelley
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=871ph5cz5l.ffs@tglx \
--to=tglx@kernel.org \
--cc=d@ilvokhin.com \
--cc=florian.fainelli@broadcom.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=radu@rendec.net \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox