Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Subject: Re: [RFC v3 01/17] perf kwork: New tool
To:     Namhyung Kim <namhyung@kernel.org>
CC:     Peter Zijlstra <peterz@infradead.org>,
        Ingo Molnar <mingo@redhat.com>,
        Arnaldo Carvalho de Melo <acme@kernel.org>,
        Mark Rutland <mark.rutland@arm.com>,
        Alexander Shishkin <alexander.shishkin@linux.intel.com>,
        Jiri Olsa <jolsa@kernel.org>, "Paul Clarke" <pc@us.ibm.com>,
        linux-kernel <linux-kernel@vger.kernel.org>,
        linux-perf-users <linux-perf-users@vger.kernel.org>
References: <20220709015033.38326-1-yangjihong1@huawei.com>
 <20220709015033.38326-2-yangjihong1@huawei.com>
 <CAM9d7cjRPSsoAk22xTO=BFQTVn+HmMZkcm7grNehHkbtRWwhgw@mail.gmail.com>
From:   Yang Jihong <yangjihong1@huawei.com>
Message-ID: <289300c6-f822-03de-9a6b-f2352421097b@huawei.com>
Date:   Thu, 28 Jul 2022 19:48:53 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <CAM9d7cjRPSsoAk22xTO=BFQTVn+HmMZkcm7grNehHkbtRWwhgw@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hello Namhyung,

On 2022/7/28 7:33, Namhyung Kim wrote:
> Hello,
> 
> On Fri, Jul 8, 2022 at 6:53 PM Yang Jihong <yangjihong1@huawei.com> wrote:
>>
>> 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.
>>
>> Test cases:
>>
>>    # perf
>>
>>     usage: perf [--version] [--help] [OPTIONS] COMMAND [ARGS]
>>
>>     The most commonly used perf commands are:
>>    <SNIP>
>>       iostat          Show I/O performance metrics
>>       kallsyms        Searches running kernel for symbols
>>       kmem            Tool to trace/measure kernel memory properties
>>       kvm             Tool to trace/measure kvm guest os
>>       kwork           Tool to trace/measure kernel work properties (latencies)
>>       list            List all symbolic event types
>>       lock            Analyze lock events
>>       mem             Profile memory accesses
>>       record          Run a command and record its profile into perf.data
>>    <SNIP>
>>     See 'perf help COMMAND' for more information on a specific command.
>>
>>    # perf kwork
>>
>>     Usage: perf kwork [<options>] {record}
>>
>>        -D, --dump-raw-trace  dump raw trace in ASCII
>>        -f, --force           don't complain, do it
>>        -k, --kwork <kwork>   list of kwork to profile
>>        -v, --verbose         be more verbose (show symbol address, etc)
>>
>>    # perf kwork record -- sleep 1
>>    [ perf record: Woken up 0 times to write data ]
>>    [ perf record: Captured and wrote 1.787 MB perf.data ]
>>
>> Signed-off-by: Yang Jihong <yangjihong1@huawei.com>
>> ---
> [SNIP]
>> +
>> +static int perf_kwork__record(struct perf_kwork *kwork,
>> +                             int argc, const char **argv)
>> +{
>> +       const char **rec_argv;
>> +       unsigned int rec_argc, i, j;
>> +       struct kwork_class *class;
>> +
>> +       const char *const record_args[] = {
>> +               "record",
>> +               "-a",
>> +               "-R",
>> +               "-m", "1024",
>> +               "-c", "1",
> 
> Please consider adding '--synth task' to skip costly synthesis
> if you don't need user space symbols.
> 
Yes, we don't need user space symbols now, I'll add this option in next 
fix patch,thanks for your suggestion.

Regards,
Jihong
> .
>