Re: [PATCH] tracing: Add bitmask-list option for human-readable bitmask display

[Steven Rostedt]

On Tue, 23 Dec 2025 17:14:35 -0500
Aaron Tomlin <atomlin@xxxxxxxxxxx> wrote:

> When dealing with 128+ logical cores, interpreting a raw hexadecimal bitmap
> to identify targeted CPUs is mentally taxing and prone to error. For
> example, if I am investigating why CPU 6 is being interrupted, I might use
> a filter such as "cpumask & CPU{6}". Seeing the resulting output as a range
> list (e.g., 0-7) rather than a hexadecimal bitmask allows one to deduce
> almost instantly which cluster of CPUs is involved in the IPI broadcast.

Should we just make all cpu bitmask range lists instead?

-- Steve