All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bixuan Cui <cuibixuan@huawei.com>
To: Alexei Budankov <abudankov@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 1/2] perf tools: add 'perf irq' to measure the hardware interrupts
Date: Thu, 14 Jan 2021 15:29:52 +0800	[thread overview]
Message-ID: <79790803-8f2e-7fca-d9d9-9c45363ab96c@huawei.com> (raw)
In-Reply-To: <03316fe6-f59b-9911-67e0-2841bb79cac7@huawei.com>



On 2021/1/13 3:50, Alexei Budankov wrote:
> Hi Bixuan,
> 
> On 12.01.2021 15:55, 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 timeconsume' to calculate the time consumed by each
>>    hardware interrupt processing function.
>>
>> Signed-off-by: Bixuan Cui <cuibixuan@huawei.com>
> Thanks for the patches. There is still something that could be improved.
> 
>> ---
>>  tools/perf/Build         |   1 +
>>  tools/perf/builtin-irq.c | 288 +++++++++++++++++++++++++++++++++++++++
>>  tools/perf/builtin.h     |   1 +
>>  tools/perf/perf.c        |   1 +
>>  4 files changed, 291 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",
> I see it works also like this:
> 
> sudo perf record -p PID -c 1 -e irq:irq_handler_entry,irq:irq_handler_exit
> sudo perf record -R -c 1 -e irq:irq_handler_entry,irq:irq_handler_exit -- find /
> 
> This -a option jointly with -p option could be made configurable from
> the command line for perf irq mode.
That's true. We can add a series of commands for 'perf irq',such as record, script and report.
So I kept the 'perf irq record'.

> 
>> +		"-R",
>> +		"-m", "1024",
> Do you see data losses with default buffer size of 512KB
> when capturing trace in your specific use case?
> 
> If not then this -m could be avoided or made configurable
> if you still need it.
Thank you for your advice, I will delete it.

  reply	other threads:[~2021-01-14  7:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 12:55 [PATCH 0/2] perf tools: add 'perf irq' to measure the hardware interrupts Bixuan Cui
2021-01-12 12:55 ` [PATCH 1/2] " Bixuan Cui
2021-01-12 19:50   ` Alexei Budankov
2021-01-14  7:29     ` Bixuan Cui [this message]
2021-01-12 12:55 ` [PATCH 2/2] perf tools: Add documentation for 'perf irq' command Bixuan Cui
2021-01-12 19:51   ` Alexei Budankov
2021-01-13  0:59 [PATCH 0/2] perf tools: add 'perf irq' to measure the hardware interrupts Bixuan Cui
2021-01-13  0:59 ` [PATCH 1/2] " 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=79790803-8f2e-7fca-d9d9-9c45363ab96c@huawei.com \
    --to=cuibixuan@huawei.com \
    --cc=abudankov@huawei.com \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.