From: tip-bot for Anshuman Khandual <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, eranian@google.com, hpa@zytor.com,
mingo@kernel.org, torvalds@linux-foundation.org,
peterz@infradead.org, khandual@linux.vnet.ibm.com,
acme@kernel.org, ak@linux.intel.com, tglx@linutronix.de
Subject: [tip:perf/core] perf/tool: Add conditional branch filter 'cond' to perf record
Date: Thu, 5 Jun 2014 07:39:38 -0700 [thread overview]
Message-ID: <tip-0fffa5df4cf3e22be4f40f6698ab9e49f3ffd6fa@git.kernel.org> (raw)
In-Reply-To: <1400743210-32289-2-git-send-email-khandual@linux.vnet.ibm.com>
Commit-ID: 0fffa5df4cf3e22be4f40f6698ab9e49f3ffd6fa
Gitweb: http://git.kernel.org/tip/0fffa5df4cf3e22be4f40f6698ab9e49f3ffd6fa
Author: Anshuman Khandual <khandual@linux.vnet.ibm.com>
AuthorDate: Thu, 22 May 2014 12:50:08 +0530
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Thu, 5 Jun 2014 12:30:19 +0200
perf/tool: Add conditional branch filter 'cond' to perf record
Adding perf record support for new branch stack filter criteria
PERF_SAMPLE_BRANCH_COND.
Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Reviewed-by: Stephane Eranian <eranian@google.com>
Reviewed-by: Andi Kleen <ak@linux.intel.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Link: http://lkml.kernel.org/r/1400743210-32289-2-git-send-email-khandual@linux.vnet.ibm.com
Cc: mpe@ellerman.id.au
Cc: benh@kernel.crashing.org
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
tools/perf/builtin-record.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/builtin-record.c b/tools/perf/builtin-record.c
index ce2cfec..378b85b 100644
--- a/tools/perf/builtin-record.c
+++ b/tools/perf/builtin-record.c
@@ -548,6 +548,7 @@ static const struct branch_mode branch_modes[] = {
BRANCH_OPT("abort_tx", PERF_SAMPLE_BRANCH_ABORT_TX),
BRANCH_OPT("in_tx", PERF_SAMPLE_BRANCH_IN_TX),
BRANCH_OPT("no_tx", PERF_SAMPLE_BRANCH_NO_TX),
+ BRANCH_OPT("cond", PERF_SAMPLE_BRANCH_COND),
BRANCH_END
};
next prev parent reply other threads:[~2014-06-05 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 7:20 [PATCH V6 1/4] perf: Add new conditional branch filter PERF_SAMPLE_BRANCH_COND Anshuman Khandual
2014-05-22 7:20 ` [PATCH V6 2/4] perf, tool: Conditional branch filter 'cond' added to perf record Anshuman Khandual
2014-06-05 14:39 ` tip-bot for Anshuman Khandual [this message]
2014-05-22 7:20 ` [PATCH V6 3/4] x86, perf: Add conditional branch filtering support Anshuman Khandual
2014-06-05 14:39 ` [tip:perf/core] perf/x86: " tip-bot for Anshuman Khandual
2014-05-22 7:20 ` [PATCH V6 4/4] perf, documentation: Description for conditional branch filter Anshuman Khandual
2014-06-05 14:40 ` [tip:perf/core] perf/documentation: Add description " tip-bot for Anshuman Khandual
2014-06-05 14:39 ` [tip:perf/core] perf: Add new conditional branch filter ' PERF_SAMPLE_BRANCH_COND' tip-bot for Anshuman Khandual
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=tip-0fffa5df4cf3e22be4f40f6698ab9e49f3ffd6fa@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 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.