mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bixuan Cui <cuibixuan@huawei.com>
To: Hagen Paul Pfeifer <hagen@jauu.net>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
	<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
	<jolsa@redhat.com>, <namhyung@kernel.org>,
	<linux-kernel@vger.kernel.org>, <john.wanghui@huawei.com>,
	<abudankov@huawei.com>, <yz.yuzhou@huawei.com>
Subject: Re: [PATCH v3 1/2] perf tools: add 'perf irq' to measure the hardware interrupts
Date: Thu, 18 Feb 2021 17:14:09 +0800	[thread overview]
Message-ID: <078a209a-087c-3fc3-d568-1a65e450b154@huawei.com> (raw)
In-Reply-To: <YBQUZ/LmiZkYSVCg@laniakea>



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

  parent reply	other threads:[~2021-02-18 10:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  1:19 [PATCH v3 0/2] " Bixuan Cui
2021-01-16  1:19 ` [PATCH v3 1/2] " Bixuan Cui
2021-01-27  7:37   ` Namhyung Kim
2021-01-27  8:38     ` Bixuan Cui
     [not found]   ` <YBQUZ/LmiZkYSVCg@laniakea>
2021-02-18  9:14     ` Bixuan Cui [this message]
2021-01-16  1:19 ` [PATCH v3 2/2] perf tools: Add documentation for 'perf irq' command Bixuan Cui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=078a209a-087c-3fc3-d568-1a65e450b154@huawei.com \
    --to=cuibixuan@huawei.com \
    --cc=abudankov@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=hagen@jauu.net \
    --cc=john.wanghui@huawei.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=yz.yuzhou@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®