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: <1340377510.1478.10.camel@leonhard>
Date:	Sat, 23 Jun 2012 00:05:10 +0900
From:	Namhyung Kim <namhyung@...il.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Jiri Olsa <jolsa@...hat.com>, David Ahern <dsahern@...il.com>
Subject: Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf
 dependency (v2)

Hi Peter,

2012-06-22 (금), 11:47 +0200, Peter Zijlstra:
> On Fri, 2012-06-22 at 14:37 +0900, Namhyung Kim wrote:
> > And then I realized that the perf record needs to know about the
> > build-id's anyway. :( So I implemented a poor man's version of elf
> > parser only for parsing the build-id info. 
> 
> Why? the very first versions didn't know about any of that nonsense :-)
> It works just fine as long as you don't go change binaries around.
> 
> That said, you did the work already, so no objection, just saying
> builtids aren't that important.

I'm not sure I understood you correctly. But 'perf record' needs to know
about the build-id's to save them to perf.data for 'perf report' later.
And 'perf archive' also needs to know about them to select necessary
binaries for the session.

-- 
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