Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1487456

[PATCH 0/2] perf, bts: Make BTS exclusive again

From Alexander Shishkin <alexander.shishkin@linux.intel.com>
Newsgroups linux.kernel
Subject [PATCH 0/2] perf, bts: Make BTS exclusive again
Date 2016-09-20 18:00 +0200
Message-ID <sjvCG-4Ws-5@gated-at.bofh.it> (permalink)
Organization linux.* mail to news gateway

Show all headers | View 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

Back to linux.kernel | Previous | NextNext in thread | Find similar | Unroll thread


Thread

[PATCH 0/2] perf, bts: Make BTS exclusive again Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-09-20 18:00 +0200
  [PATCH 2/2] perf: Limit matching exclusive events to one PMU Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-09-20 18:00 +0200
    [tip:perf/urgent] perf/core: Limit matching exclusive events to one  PMU tip-bot for Alexander Shishkin <tipbot@zytor.com> - 2016-09-22 16:10 +0200
  [PATCH 1/2] perf/x86/intel/bts: Make it an exclusive PMU Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-09-20 18:00 +0200
    [tip:perf/urgent] perf/x86/intel/bts: Make it an exclusive PMU tip-bot for Alexander Shishkin <tipbot@zytor.com> - 2016-09-22 16:10 +0200

csiph-web