From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"Liang, Kan" <kan.liang@intel.com>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 0/5] perf: add support for capturing skid IP
Date: Thu, 15 Jun 2017 16:18:16 -0700 [thread overview]
Message-ID: <20170615231816.GD4789@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBQCNqp_Lze6Va5RgFL_sQYEBVPmeLj5WcCOF99PeS=P4w@mail.gmail.com>
> Looking at this approach, the user interface is straightforward,
> implementation in the x86 code is a bit more hairy because of the way
> the branch_stack is captured, via the cpuc->lbr_entries. If you assume
> that SKID_IP cannot be used with any other branch stack mode, then it
> is easy. It becomes messy if you don't.
That should be fine. After all if you have real LBRs you don't need
the skid IP.
-Andi
next prev parent reply other threads:[~2017-06-15 23:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 13:56 [PATCH 0/5] perf: add support for capturing skid IP Stephane Eranian
2017-06-15 13:56 ` [PATCH 1/5] perf/core: add PERF_SAMPLE_SKID_IP record type Stephane Eranian
2017-06-15 13:56 ` [PATCH 2/5] perf/x86: add PERF_SAMPLE_SKID_IP support for X86 PEBS Stephane Eranian
2017-06-15 15:40 ` Liang, Kan
2017-06-15 16:39 ` Stephane Eranian
2017-06-15 17:18 ` Liang, Kan
2017-06-15 19:19 ` Stephane Eranian
2017-06-15 13:56 ` [PATCH 3/5] perf/tools: add support for PERF_SAMPLE_SKID_IP Stephane Eranian
2017-06-15 13:56 ` [PATCH 4/5] perf/record: add support for sampling skid ip Stephane Eranian
2017-06-15 13:56 ` [PATCH 5/5] perf/script: add support for " Stephane Eranian
2017-06-15 15:10 ` [PATCH 0/5] perf: add support for capturing skid IP Andi Kleen
2017-06-15 16:44 ` Stephane Eranian
2017-06-15 17:23 ` Andi Kleen
2017-06-15 19:35 ` Stephane Eranian
2017-06-15 20:02 ` Andi Kleen
2017-06-15 20:20 ` Stephane Eranian
2017-06-15 22:28 ` Stephane Eranian
2017-06-15 23:18 ` Andi Kleen [this message]
2017-06-16 6:52 ` Stephane Eranian
2017-06-16 16:06 ` Andi Kleen
2017-06-16 17:08 ` Stephane Eranian
2017-06-16 17:12 ` Stephane Eranian
2017-06-16 17:50 ` Andi Kleen
2017-06-16 19:15 ` Stephane Eranian
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=20170615231816.GD4789@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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