From: Alexei Budankov <abudankov@huawei.com>
To: Bixuan Cui <cuibixuan@huawei.com>, <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>
Cc: <john.wanghui@huawei.com>
Subject: Re: [PATCH v2 1/2] perf tools: add 'perf irq' to measure the hardware interrupts
Date: Thu, 14 Jan 2021 12:32:05 +0300 [thread overview]
Message-ID: <4ad7a048-8982-577b-b7c0-ca7e25f901d6@huawei.com> (raw)
In-Reply-To: <20210114074852.13231-2-cuibixuan@huawei.com>
On 14.01.2021 10:48, Bixuan Cui wrote:
> Add 'perf irq' to trace/measure the hardware interrupts.
>
> Now three functions are provided:
> 1. 'perf irq record <command>' to record the irq handler events.
> 2. 'perf irq script' to see a detailed trace of the workload that
> was recorded.
> 3. 'perf irq report' to calculate the time consumed by each
> hardware interrupt processing function.
>
> Signed-off-by: Bixuan Cui <cuibixuan@huawei.com>
> ---
> tools/perf/Build | 1 +
> tools/perf/builtin-irq.c | 287 +++++++++++++++++++++++++++++++++++++++
> tools/perf/builtin.h | 1 +
> tools/perf/perf.c | 1 +
> 4 files changed, 290 insertions(+)
> create mode 100644 tools/perf/builtin-irq.c
<SNIP>
> +static int __cmd_record(int argc, const char **argv)
> +{
> + unsigned int rec_argc, i, j;
> + const char **rec_argv;
> + const char * const record_args[] = {
> + "record",
> + "-a",
Could you please make it configurable from the command line
jointly with -p option?
> + "-R",
> + "-c", "1",
> + "-e", "irq:irq_handler_entry",
> + "-e", "irq:irq_handler_exit",
> + };
Thanks,
Alexei
next prev parent reply other threads:[~2021-01-14 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 7:48 [PATCH v2 0/2] " Bixuan Cui
2021-01-14 7:48 ` [PATCH v2 1/2] " Bixuan Cui
2021-01-14 9:32 ` Alexei Budankov [this message]
2021-01-14 7:48 ` [PATCH v2 2/2] perf tools: Add documentation for 'perf irq' command Bixuan Cui
2021-01-14 9:19 ` Alexei Budankov
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=4ad7a048-8982-577b-b7c0-ca7e25f901d6@huawei.com \
--to=abudankov@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=cuibixuan@huawei.com \
--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 \
/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®