mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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>,
	tglx@linutronix.de,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: [PATCH 0/2] perf, bts: Make BTS exclusive again
Date: Tue, 20 Sep 2016 18:48:09 +0300	[thread overview]
Message-ID: <20160920154811.3255-1-alexander.shishkin@linux.intel.com> (raw)

Hi Peter,

While looking at something else I noticed that the exclusive event
filter only allows one such event per context, whereas it should allow
one such event from each PMU that has PERF_PMU_CAP_EXCLUSIVE. At the
same time, intel_bts PMU doesn't even have this capability set (which
is why on systems that allow coexistance of PT and BTS it still works,
see ccbebba4c6 for more context).

Alexander Shishkin (2):
  perf/x86/intel/bts: Make it an exclusive PMU
  perf: Limit matching exclusive events to one PMU

 arch/x86/events/intel/bts.c | 3 ++-
 kernel/events/core.c        | 2 +-
 2 files changed, 3 insertions(+), 2 deletions(-)

-- 
2.9.3

             reply	other threads:[~2016-09-20 15:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-20 15:48 Alexander Shishkin [this message]
2016-09-20 15:48 ` [PATCH 1/2] perf/x86/intel/bts: Make it an exclusive PMU Alexander Shishkin
2016-09-22 14:00   ` [tip:perf/urgent] " tip-bot for Alexander Shishkin
2016-09-20 15:48 ` [PATCH 2/2] perf: Limit matching exclusive events to one PMU Alexander Shishkin
2016-09-22 14:01   ` [tip:perf/urgent] perf/core: " 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=20160920154811.3255-1-alexander.shishkin@linux.intel.com \
    --to=alexander.shishkin@linux.intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@infradead.org \
    --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