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]
Date:	Thu, 5 Jul 2012 18:09:18 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Namhyung Kim <namhyung@...il.com>
Cc:	Jiri Olsa <jolsa@...hat.com>, acme@...hat.com,
	a.p.zijlstra@...llo.nl, mingo@...e.hu, paulus@...ba.org,
	cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com,
	linux-kernel@...r.kernel.org, tglx@...utronix.de,
	andi@...stfloor.org, drepper@...il.com
Subject: Re: [PATCHv3 0/3] perf tool: Add new event group management

On Mon, Jul 2, 2012 at 3:11 PM, Namhyung Kim <namhyung@...il.com> wrote:
> 2012-07-02 (월), 12:15 +0200, Jiri Olsa:
>> On Mon, Jul 02, 2012 at 10:53:44AM +0900, Namhyung Kim wrote:
>> > Just a question, is there a way to know about the grouping at perf
>> > report time?
>>
>> nope, AFAIK only ID and perf_event_attr is stored for event
>> grouping is known only for record time
>>
>
> I heard that Arnaldo (or Stephane) wanted to make perf report
> group-aware or such so that it can show related events together. But to
> do that, it seems we need to change the data file format first, right?
>
Yes, you'd like something like that. The idea is to use an event to sample
and the others to compute event deltas. For instance, how many loads/stores
instructions retired for every 100k instructions retired. For that you need
grouping. The kernel supports this already, the perf tool does not.

I don't  think you need to change the file format. Everything is there
already in the headers. OF course, you perf report needs to detect
this mode and adjust the output. IF not, then it should only display
samples coming from the first event. Not clear how you'd display
the information in perf report or perf annotate at this point yet.

> Any idea?
>
>
> --
> Regards,
> Namhyung Kim
>
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ