On Mon, Oct 19, 2026 at 8:26 PM Steven Rostedt <[email protected]> wrote: > > On Mon, 19 Oct 2026 19:24:17 +0200 > Roman Storozhenko <[email protected]> wrote: > > > I've renamed the header to arch/riscv/include/asm/tlb_trace.h > > in v7. I prefer this over riscv_trace.h because the latter > > sounds too generic for a header dedicated to TLB tracing. > > > > Did you have a broader use in mind, such as including other > > RISC-V tracepoints in this header? > > > > If you still prefer riscv_trace.h, I'm happy to reconsider. > > Either riscv_trace.h or tlb_trace.h in the riscv directory is fine with me. > It's more of a decision for the RISCV maintainers. If you plan on having > more RISCV specific trace events, do you want them all in one header, or > will each have their own "trace_*.h" header? > > I'm fine either way, as long as they are named with "trace" in them in > order to acknowledge that they define trace events. > > -- Steve
Thanks for the clarification, Steve. I'll keep tlb_trace.h for TLB-specific events. If I introduce tracepoints for other RISC-V subsystems in the future, I'd prefer separate headers following the <subsystem_name>_trace.h naming convention. -- Kind regards, Roman 'Hedin' Storozhenko
