On Sun, 08 Nov 2026, Nathan Chancellor wrote: > > On Sun, Nov 08, 2026 at 06:59:45PM +0000, Julian Braha wrote: > > > > I think this tool may belong in scripts/ due to the kbuild integration, > > as was mentioned in the past on another tool review: > > > > https://lore.kernel.org/linux-kbuild/20260428183101.GA3304253@ax162/ > > Yeah, while I would prefer for the script to live in scripts/ due to > being called from Kbuild, I am not sure if the rules/schemas belong > there? > > It might be better to keep everything in tools/ for that reason, > especially if this may be called externally, but I am open to other > thoughts. >
I would prefer to keep it under tools/ as well. Because of the PREEMPT_RT policy, and the possible extra policies from ELISA, etc. This is why one of the development rules at the top of the Python script, at patch 03/10, is: The tool must not depend on being run inside the kernel source tree. This simplifies invocation, testing and possible future packaging. So, upon (hopefully) including this tool mainline, I'd send a patch to the Debian kernel team to create a separate Debian package from the kernel sources for it. That is, exactly like what they're now doing with perf. (v2 of this series will add versioning support to the schemas; thus making the tool's support for packaging stronger as well.) Thanks! -- Ahmed S. Darwish Linutronix GmbH

