| 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
| ||
|
Message-ID: <20150223174448.GE27767@tassilo.jf.intel.com> Date: Mon, 23 Feb 2015 09:44:48 -0800 From: Andi Kleen <ak@...ux.intel.com> To: Peter Zijlstra <peterz@...radead.org> Cc: kan.liang@...el.com, linux-kernel@...r.kernel.org, mingo@...hat.com, acme@...nel.org Subject: Re: [RFC PATCH 1/1] proc: introduce /proc/<pid>/lbr_stack On Mon, Feb 23, 2015 at 05:49:57PM +0100, Peter Zijlstra wrote: > On Mon, Feb 23, 2015 at 03:43:41AM +0000, kan.liang@...el.com wrote: > > From: Kan Liang <kan.liang@...el.com> > > > > Haswell has a new feature that utilizes the existing Last Branch Record > > facility to record call chains. It has been implemented in perf. The > > call chains information is saved during perf event context. > > > > This patch exposes a /proc/<pid>/lbr_stack file that shows the saved LBR > > call chain information. > > But why? I mean, this thing is only useful if you have a concurrently > running perf record that selects the LBR-stack stuff. > > And if you have that, you might as well look at its output instead. Why > add this unconditional proc file that doesn't function on its own? perf record doesn't show where you're currently blocked. -Andi -- ak@...ux.intel.com -- Speaking for myself only -- 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