All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: Noah Luther <nluther@vt.edu>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: perf branch
Date: Mon, 14 Apr 2014 08:53:16 -0400	[thread overview]
Message-ID: <534BDA3C.7080603@codeaurora.org> (raw)
In-Reply-To: <CAH+i1GK4QdEzoa05PUN-Zx8Gzr2-w0RY631a9MzvTvyMAs1fGg@mail.gmail.com>

Hi Noah,

On 04/13/2014 11:55 PM, Noah Luther wrote:
> Hello,
> 
> I am trying to use perf to trace branches as described by the 'perf
> branch' subcommand. Is there support through perf_event_open to access
> the buffer storing branch traces? I saw Akihiro Nagai's presentation
> on 'perf branch', but haven't yet figured out how to enable BTS and
> access the buffer based on the documentation on this page:
> 
> http://web.eece.maine.edu/~vweaver/projects/perf_events/perf_event_open.html
> 
> If there are any resources that might be of use to me, I would
> appreciate any assistance.

In the past I've found the test suite to be a useful reference. Here's a test
that looks like it might serve as a jumping-off point.

https://github.com/deater/perf_event_tests/blob/master/tests/record_sample/sample_branch_stack.c

Regards,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

  reply	other threads:[~2014-04-14 12:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-14  3:55 perf branch Noah Luther
2014-04-14 12:53 ` Christopher Covington [this message]
2014-04-14 17:41 ` 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=534BDA3C.7080603@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=nluther@vt.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.