From: Andy Lutomirski <luto@amacapital.net>
To: "Yan, Zheng" <zheng.z.yan@intel.com>, linux-kernel@vger.kernel.org
Cc: a.p.zijlstra@chello.nl, mingo@kernel.org, acme@infradead.org,
eranian@google.com, andi@firstfloor.org
Subject: Re: [PATCH v3 00/14] perf, x86: Haswell LBR call stack support
Date: Tue, 25 Feb 2014 18:39:43 -0800 [thread overview]
Message-ID: <530D53EF.9090706@amacapital.net> (raw)
In-Reply-To: <1392703661-15104-1-git-send-email-zheng.z.yan@intel.com>
On 02/17/2014 10:07 PM, Yan, Zheng wrote:
>
> This patch series adds LBR call stack support. User can enabled/disable
> this through an sysfs attribute file in the CPU PMU directory:
> echo 1 > /sys/bus/event_source/devices/cpu/lbr_callstack
This seems like an unpleasant way to control this. It would be handy to
be able to control this as an option to perf record.
--Andy
next prev parent reply other threads:[~2014-02-26 2:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 6:07 [PATCH v3 00/14] perf, x86: Haswell LBR call stack support Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 01/14] perf, x86: Reduce lbr_sel_map size Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 02/14] perf, core: introduce pmu context switch callback Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 03/14] perf, x86: use context switch callback to flush LBR stack Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 04/14] perf, x86: Basic Haswell LBR call stack support Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 05/14] perf, core: pmu specific data for perf task context Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 06/14] perf, core: always switch pmu specific data during context switch Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 07/14] perf, x86: track number of events that use LBR callstack Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 08/14] perf, x86: allocate space for storing LBR stack Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 09/14] perf, x86: Save/resotre LBR stack during context switch Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 10/14] perf, core: simplify need branch stack check Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 11/14] perf, core: Pass perf_sample_data to perf_callchain() Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 12/14] perf, x86: use LBR call stack to get user callchain Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 13/14] perf, x86: enable LBR callstack when recording callchain Yan, Zheng
2014-02-18 6:07 ` [PATCH v3 14/14] perf, x86: Discard zero length call entries in LBR call stack Yan, Zheng
2014-02-23 19:47 ` [PATCH v3 00/14] perf, x86: Haswell LBR call stack support Stephane Eranian
2014-02-24 1:07 ` Yan, Zheng
2014-02-24 7:14 ` Peter Zijlstra
2014-02-26 2:39 ` Andy Lutomirski [this message]
2014-02-26 7:04 ` Stephane Eranian
2014-02-26 8:57 ` Yan, Zheng
2014-02-26 16:03 ` Andy Lutomirski
2014-02-26 18:55 ` Andi Kleen
2014-02-26 18:59 ` Andy Lutomirski
2014-02-26 19:19 ` David Ahern
2014-02-26 19:25 ` Andy Lutomirski
2014-02-26 20:14 ` David Ahern
2014-02-26 20:26 ` Andy Lutomirski
2014-04-09 11:48 ` Peter Zijlstra
2014-04-09 16:48 ` Andi Kleen
2014-04-09 17:40 ` Andi Kleen
2014-02-26 20:32 ` Peter Zijlstra
2014-02-26 20:53 ` Andi Kleen
2014-02-26 21:15 ` Peter Zijlstra
2014-02-26 21:33 ` Andi Kleen
2014-02-26 21:34 ` David Ahern
2014-02-26 21:42 ` Andi Kleen
2014-02-27 9:09 ` Stephane Eranian
2014-02-27 12:35 ` Ingo Molnar
2014-02-27 16:08 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=530D53EF.9090706@amacapital.net \
--to=luto@amacapital.net \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=zheng.z.yan@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).