linux-kernel - RE: [PATCH RFC V3 3/5] perf,tool: partial time support

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:	Wed, 15 Jul 2015 19:03:38 +0000
From:	"Liang, Kan" <kan.liang@...el.com>
To:	Namhyung Kim <namhyung@...nel.org>
CC:	"acme@...nel.org" <acme@...nel.org>,
	"jolsa@...nel.org" <jolsa@...nel.org>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Hunter, Adrian" <adrian.hunter@...el.com>
Subject: RE: [PATCH RFC V3 3/5] perf,tool: partial time support



> 
> However, perf_evlist__id_hdr_size() seems to be affected also.  Are you
> sure it's okay too?
> 
Yes.
id_hdr_size is calculated according to the first event. It impacts 
perf tool generated COMM, MMAP and FORK events.
But all of these events have same and position fixed IDENTIFIER, 0.
When parsing the events by perf_evlist__event2evsel, id 0 always
return first event.
So only first event will be involved to parse perf tool generated
COMM, MMAP and FORK events. TIME setting from other events
doesn’t impact.

Thanks,
Kan