From: Yang Jihong <yangjihong1@huawei.com>
To: "Paul A. Clarke" <pc@us.ibm.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<mark.rutland@arm.com>, <alexander.shishkin@linux.intel.com>,
<jolsa@kernel.org>, <namhyung@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>
Subject: Re: [RFC 00/13] perf: Add perf kwork
Date: Thu, 23 Jun 2022 09:02:45 +0800 [thread overview]
Message-ID: <3cccc03a-c2bc-91d9-60b9-daf180c6b108@huawei.com> (raw)
In-Reply-To: <YrMuQXIn9DdhZl2w@li-be644d4c-2c59-11b2-a85c-bc3dba3ed00b.ibm.com>
Hello,
On 2022/6/22 22:59, Paul A. Clarke wrote:
> On Mon, Jun 13, 2022 at 05:45:52PM +0800, Yang Jihong wrote:
>> Sometimes, we need to analyze time properties of kernel work such as irq,
>> softirq, and workqueue, such as delay and running time of specific interrupts.
>> Currently, these events have kernel tracepoints, but perf tool does not
>> directly analyze the delay of these events
>>
>> The perf-kwork tool is used to trace time properties of kernel work
>> (such as irq, softirq, and workqueue), including runtime, latency,
>> and timehist, using the infrastructure in the perf tools to allow
>> tracing extra targets
>>
>> test case:
>>
>> # perf kwork report
>>
>> Kwork Name | Cpu | Total Runtime | Frequency | Max runtime | Max runtime start | Max runtime end |
>> ---------------------------------------------------------------------------------------------------------------------------
>> (s)RCU:9 | 0007 | 3.488 ms | 1258 | 0.145 ms | 3398384.220013 s | 3398384.220157 s |
>> (s)NET_RX:3 | 0003 | 1.866 ms | 156 | 0.042 ms | 3398385.629764 s | 3398385.629806 s |
>> (s)TIMER:1 | 0000 | 1.799 ms | 117 | 0.055 ms | 3398385.568033 s | 3398385.568088 s |
>> (w)0xffff9c66e563ee98 | 0006 | 1.561 ms | 5 | 0.351 ms | 3398384.060021 s | 3398384.060371 s |
>
> What units are used for "Frequency"? It would be helpful to include somewhere.
This refers to the number of event in the trace period.
Thanks,
Jihong
>
> PC
> .
>
next prev parent reply other threads:[~2022-06-23 1:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 9:45 Yang Jihong
2022-06-13 9:45 ` [RFC 01/13] perf kwork: New tool Yang Jihong
2022-06-14 21:43 ` Namhyung Kim
2022-06-15 1:38 ` Yang Jihong
2022-06-13 9:45 ` [RFC 02/13] perf kwork: Add irq record support Yang Jihong
2022-06-13 9:45 ` [RFC 03/13] perf kwork: Add softirq " Yang Jihong
2022-06-13 9:45 ` [RFC 04/13] perf kwork: Add workqueue " Yang Jihong
2022-06-13 9:45 ` [RFC 05/13] tools lib: Add list_last_entry_or_null Yang Jihong
2022-06-13 9:45 ` [RFC 06/13] perf kwork: Implement perf kwork report Yang Jihong
2022-06-14 21:49 ` Namhyung Kim
2022-06-15 3:12 ` Yang Jihong
2022-06-15 22:01 ` Namhyung Kim
2022-06-16 1:31 ` Yang Jihong
2022-06-13 9:45 ` [RFC 07/13] perf kwork: Add irq report support Yang Jihong
2022-06-13 9:46 ` [RFC 08/13] perf kwork: Add softirq " Yang Jihong
2022-06-13 9:46 ` [RFC 09/13] perf kwork: Add workqueue " Yang Jihong
2022-06-14 21:54 ` Namhyung Kim
2022-06-15 3:22 ` Yang Jihong
2022-06-15 21:56 ` Namhyung Kim
2022-06-16 1:42 ` Yang Jihong
2022-06-13 9:46 ` [RFC 10/13] perf kwork: Implement perf kwork latency Yang Jihong
2022-06-13 9:46 ` [RFC 11/13] perf kwork: Add softirq latency support Yang Jihong
2022-06-13 9:46 ` [RFC 12/13] perf kwork: Add workqueue " Yang Jihong
2022-06-13 9:46 ` [RFC 13/13] perf kwork: Implement perf kwork timehist Yang Jihong
2022-06-22 14:59 ` [RFC 00/13] perf: Add perf kwork Paul A. Clarke
2022-06-23 1:02 ` Yang Jihong [this message]
2022-06-23 14:25 ` Paul A. Clarke
2022-06-24 1:26 ` Yang Jihong
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=3cccc03a-c2bc-91d9-60b9-daf180c6b108@huawei.com \
--to=yangjihong1@huawei.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pc@us.ibm.com \
--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®