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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 14 May 2016 08:43:03 -0600 From: David Ahern <dsahern@...il.com> To: He Kuang <hekuang@...wei.com>, peterz@...radead.org, mingo@...hat.com, acme@...nel.org, alexander.shishkin@...ux.intel.com, jolsa@...hat.com, wangnan0@...wei.com, jpoimboe@...hat.com, ak@...ux.intel.com, eranian@...gle.com, namhyung@...nel.org, adrian.hunter@...el.com, sukadev@...ux.vnet.ibm.com, masami.hiramatsu.pt@...achi.com, tumanova@...ux.vnet.ibm.com, kan.liang@...el.com, penberg@...nel.org Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH v3 3/7 UPDATE] perf tools: Add option for the path of buildid dsos under symfs On 5/14/16 2:19 AM, He Kuang wrote: > In the cross-platform perf record/script scenario, we need vdsos in > buildid-cache dir and other libs in symfs dir at the same time. For > the reason that to have every single file opened by perf is relative > to symfs dirctory, perf skips the buildid dir if symfs is given. > > This patch references the buildid dir under symfs if '--symfs' is > used, and adds new option '--dso-prefix' to specify the subdir path in > symfs which contains the buildid dsos. In the previous version of this patch you just wanted to drop the symfs check. That means there is a path that perf searches for buildid files and reading it worked for you. Why is adding symsfs to that path not enough? ie., Why do you need to specify a different location under the symfs?
Powered by blists - more mailing lists