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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20251224085848.26387f5d@gandalf.local.home>
Date: Wed, 24 Dec 2025 08:58:48 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Aaron Tomlin <atomlin@...mlin.com>
Cc: mhiramat@...nel.org, mark.rutland@....com,
 mathieu.desnoyers@...icios.com, corbet@....net, sean@...e.io,
 linux-kernel@...r.kernel.org, linux-trace-kernel@...r.kernel.org,
 linux-doc@...r.kernel.org
Subject: Re: [PATCH] tracing: Add bitmask-list option for human-readable
 bitmask display

On Tue, 23 Dec 2025 17:14:35 -0500
Aaron Tomlin <atomlin@...mlin.com> 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