linux-kernel - Re: [PATCH 0/2] Enhance the init of vmlinux

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: <20151126195210.GJ28162@kernel.org>
Date:	Thu, 26 Nov 2015 16:52:10 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Ekaterina Tumanova <tumanova@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, borntraeger@...ibm.com,
	yarygin@...ux.vnet.ibm.com, a.p.zijlstra@...llo.nl,
	mingo@...hat.com, namhyung@...nel.org, adrian.hunter@...el.com,
	wangnan0@...wei.com, naveen.n.rao@...ux.vnet.ibm.com,
	dsahern@...il.com, jolsa@...nel.org
Subject: Re: [PATCH 0/2] Enhance the init of vmlinux_path and add new path

Em Wed, Nov 25, 2015 at 05:32:44PM +0100, Ekaterina Tumanova escreveu:
> These pathset improves perf processing of the paths to vmlinux files:
> 1. it refactors the vmlinux_path__init procedure, to allow a simple
> usage in future: instead of adding several lines for every future vmlinux path,
> make it possible to simply add a path itself (1 line) to an array.
> 2. Some distibutions separate debuginfo to vmlinux.debug file. This patchset
> adds a path to vmlinux.debug, so that perf could use its symbols.
> 
> Ekaterina Tumanova (2):
>   perf: Refactor vmlinux_path_init
>   perf: add the path to vmlinux.debug

Applied both, after renaming vmlinux_path__update() to
vmlinux_path__add(), as this "adds" entries to vmlinux_path.

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