From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, linux-kernel@vger.kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] perf, tools: Implement branch_type event parameter
Date: Thu, 13 Oct 2016 13:32:52 +0200 [thread overview]
Message-ID: <20161013113252.GA8036@krava> (raw)
In-Reply-To: <1476306127-19721-1-git-send-email-andi@firstfloor.org>
On Wed, Oct 12, 2016 at 02:02:06PM -0700, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> It can be useful to specify branch type state per event, for example
> if we want to collect both software trace points and last branch PMU
> events in a single collection. Currently this doesn't work because
> the software trace point errors out with -b.
>
> There was already a branch-type parameter to configure branch sample
> types per event in the parser, but it was stubbed out. This patch
> implements the necessary plumbing to actually enable it.
>
> Now
>
> perf record -e sched:sched_switch,cpu/cpu-cycles,branch_type=any/ ...
>
> works
>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
Acked-by: Jiri Olsa <jolsa@redhat.com>
thanks,
jirka
next prev parent reply other threads:[~2016-10-13 11:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 21:02 [PATCH 1/2] perf, tools: Implement branch_type event parameter Andi Kleen
2016-10-12 21:02 ` [PATCH 2/2] perf, tools: Add documentation for perf user event parameters Andi Kleen
2016-10-13 11:33 ` Jiri Olsa
2016-10-13 11:32 ` Jiri Olsa [this message]
2016-10-24 18:56 ` [tip:perf/core] perf tools: Implement branch_type event parameter tip-bot for 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=20161013113252.GA8036@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.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