linux-kernel - Re: [PATCH 3/3] perf script: Align event name properly

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 for Android: free password hash cracker in your pocket

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

Message-ID: <5657188B.1030407@gmail.com>
Date:	Thu, 26 Nov 2015 07:34:51 -0700
From:	David Ahern <dsahern@...il.com>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	Jiri Olsa <jolsa@...nel.org>,
	Arnaldo Carvalho de Melo <acme@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Namhyung Kim <namhyung@...nel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 3/3] perf script: Align event name properly

On 11/26/15 7:30 AM, Jiri Olsa wrote:
> On Thu, Nov 26, 2015 at 07:25:17AM -0700, David Ahern wrote:
>> On 11/26/15 6:55 AM, Jiri Olsa wrote:
>>> Adding code to align event names, so we get aligned output
>>> in case of multiple events with different names.
>>>
>>> Before:
>>>    $ perf script
>>>    :13757 13757 163918.230829: cpu/mem-snp-none/P: ffff88085f20d010
>>>    :13757 13757 163918.230832: cpu/mem-loads,ldlat=30/P:     7f5a5f719f00
>>>    :13757 13757 163918.230835: cpu/mem-loads,ldlat=30/P:     7f5a5f719f00
>>>    :13758 13758 163918.230838: cpu/mem-snp-none/P: ffff88085f4ad810
>>>    :13758 13758 163918.154093: cpu/mem-stores/P: ffff88085bb53f28
>>>    :13757 13757 163918.155264: cpu/mem-snp-hitm/P:           601080
>>>    ...
>>>
>>
>> What's up with the ":13757" for the process name?
>
> hum, fallback if the name's not resolved? I'll check..

right, but I thought those were fixed. How is there a SAMPLE for a task 
without a COMM.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/