[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4becabb-3b8d-b35b-caa9-db106ed3fbb8@huawei.com>
Date: Wed, 27 Jul 2022 08:38:53 +0800
From: Yang Jihong <yangjihong1@...wei.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
CC: <peterz@...radead.org>, <mingo@...hat.com>, <mark.rutland@....com>,
<alexander.shishkin@...ux.intel.com>, <jolsa@...nel.org>,
<namhyung@...nel.org>, <pc@...ibm.com>,
<linux-kernel@...r.kernel.org>, <linux-perf-users@...r.kernel.org>
Subject: Re: [RFC v3 01/17] perf kwork: New tool
Hello,
On 2022/7/27 1:27, Arnaldo Carvalho de Melo wrote:
> Em Sat, Jul 09, 2022 at 09:50:17AM +0800, Yang Jihong escreveu:
>> 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.
>>
>> This is the first commit to reuse perf_record framework code to
>> implement a simple record function, kwork is not supported currently.
>
> So, since I have to fix some issues I'm adding small stylistic changes,
> starting with this:
>
>
> - multiline if/for blocks need {}
>
> - remove needless spaces between variable declaration + initialization.
>
> - Arnaldo
>
OK, I'll fix it in next version.
Regards,
Jihong
Powered by blists - more mailing lists