linux-kernel - Re: [RFC 01/13] perf kwork: New tool

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <f7ce4fd3-9631-015a-8b1f-81f704e82719@huawei.com>
Date:   Wed, 15 Jun 2022 09:38:50 +0800
From:   Yang Jihong <yangjihong1@...wei.com>
To:     Namhyung Kim <namhyung@...nel.org>
CC:     Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Arnaldo Carvalho de Melo <acme@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        Jiri Olsa <jolsa@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        linux-perf-users <linux-perf-users@...r.kernel.org>
Subject: Re: [RFC 01/13] perf kwork: New tool

Hello, Namhyung

On 2022/6/15 5:43, Namhyung Kim wrote:
> Hello,
> 
> On Mon, Jun 13, 2022 at 2:48 AM Yang Jihong <yangjihong1@...wei.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:
>>
>>    # perf kwork -h
>>
>>     Usage: perf kwork [<options>] {record|report|latency|timehist}
>>
>>        -D, --dump-raw-trace  dump raw trace in ASCII
>>        -f, --force           don't complain, do it
>>        -k, --kwork <kwork>   list of kwork to profile (irq, softirq, workqueue etc)
>>        -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.696 MB perf.data ]
>>
>>    # perf kwork report -h
>>
>>     Usage: perf kwork report [<options>]
>>
>>        -C, --cpu <cpu>       list of cpus to profile
>>        -i, --input <file>    input file name
>>        -n, --name <name>     event name to profile
>>        -s, --sort <key[,key2...]>
>>                              sort by key(s): runtime, max, freq
>>        -S, --with-summary    Show summary with statistics
>>            --time <str>      Time span for analysis (start,stop)
>>
>>    # perf kwork latency -h
>>
>>     Usage: perf kwork latency [<options>]
>>
>>        -C, --cpu <cpu>       list of cpus to profile
>>        -i, --input <file>    input file name
>>        -n, --name <name>     event name to profile
>>        -s, --sort <key[,key2...]>
>>                              sort by key(s): avg, max, freq
>>            --time <str>      Time span for analysis (start,stop)
>>
>>    # perf kwork timehist -h
>>
>>     Usage: perf kwork timehist [<options>]
>>
>>        -C, --cpu <cpu>       list of cpus to profile
>>        -g, --call-graph      Display call chains if present
>>        -i, --input <file>    input file name
>>        -k, --vmlinux <file>  vmlinux pathname
>>        -n, --name <name>     event name to profile
>>            --kallsyms <file>
>>                              kallsyms pathname
>>            --max-stack <n>   Maximum number of functions to display backtrace.
>>            --symfs <directory>
>>                              Look for files with symbols relative to this directory
>>            --time <str>      Time span for analysis (start,stop)
> 
> I think you can add this and the documentation when you
> actually add the functionality later.
> 
OK, I'll fix in next version.


Thanks，
Jihong
.