linux-kernel - Re: [PATCH v3 1/2] perf tools: add 'perf irq' to measure the hardware interrupts

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>] [day] [month] [year] [list]

Date:   Thu, 18 Feb 2021 17:14:09 +0800
From:   Bixuan Cui <cuibixuan@...wei.com>
To:     Hagen Paul Pfeifer <hagen@...u.net>
CC:     <peterz@...radead.org>, <mingo@...hat.com>, <acme@...nel.org>,
        <mark.rutland@....com>, <alexander.shishkin@...ux.intel.com>,
        <jolsa@...hat.com>, <namhyung@...nel.org>,
        <linux-kernel@...r.kernel.org>, <john.wanghui@...wei.com>,
        <abudankov@...wei.com>, <yz.yuzhou@...wei.com>
Subject: Re: [PATCH v3 1/2] perf tools: add 'perf irq' to measure the hardware
 interrupts



On 2021/1/29 21:57, Hagen Paul Pfeifer wrote:
> Idea: why now pre-calc the max IRQ name length and adjust the columns
> dynamically? Time consume us, entry time and exit time can be threatet static
> in (max) length lenght. This overlong, static ASCII lines are no pleasure! ;-)
> 
> Furthermore, why not a --format feature?
> *perf irq report --format csv* option? Your human readable ASCII version is
> okay, but often you had thousands of IRQs where just one IRQ is an outliner.
> Pipe the output to numpy and matplotlib is often the required post-precessing
> step, but parsing the ASCII output is tortuous.
> 
Good idea. In fact, I plan to output part of (maximum) data.
I'll consider adding '--format csv*' option.

Thanks
Bixuan Cui
> hgn