From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org, vince@deater.net,
eranian@google.com, Arnaldo Carvalho de Melo <acme@infradead.org>,
Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 0/2] perf/x86/intel/pt: Misc updates
Date: Fri, 27 Jan 2017 17:16:42 +0200 [thread overview]
Message-ID: <20170127151644.8585-1-alexander.shishkin@linux.intel.com> (raw)
Hi Peter,
Here I have two small updates. Branch tracing can now be disabled
so that we have more bandwidth for other things that PT may log,
such as power events. The latter, along with the PTWRITE, didn't
get their own format strings before, so adding them now.
Alexander Shishkin (2):
perf/x86/intel/pt: Add format strings for PTWRITE and power event
tracing
perf/x86/intel/pt: Allow disabling branch tracing
arch/x86/events/intel/pt.c | 42 +++++++++++++++++++++++++++++++++++++++++-
arch/x86/events/intel/pt.h | 1 +
2 files changed, 42 insertions(+), 1 deletion(-)
--
2.11.0
next reply other threads:[~2017-01-27 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 15:16 Alexander Shishkin [this message]
2017-01-27 15:16 ` [PATCH 1/2] perf/x86/intel/pt: Add format strings for PTWRITE and power event tracing Alexander Shishkin
2017-02-01 10:21 ` [tip:perf/core] " tip-bot for Alexander Shishkin
2017-01-27 15:16 ` [PATCH 2/2] perf/x86/intel/pt: Allow disabling branch tracing Alexander Shishkin
2017-02-01 10:17 ` Ingo Molnar
2017-02-01 16:49 ` Alexander Shishkin
2017-02-02 10:14 ` Alexander Shishkin
2017-02-06 14:41 ` [PATCH] " Alexander Shishkin
2017-02-06 15:58 ` Andi Kleen
2017-02-06 16:05 ` Alexander Shishkin
2017-02-06 17:19 ` Andi Kleen
2017-04-27 8:11 ` Adrian Hunter
2017-03-30 8:33 ` [tip:perf/core] perf/x86/intel/pt: Allow the disabling of " tip-bot for Alexander Shishkin
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=20170127151644.8585-1-alexander.shishkin@linux.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=bp@suse.de \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vince@deater.net \
/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
Powered by JetHome