From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932913AbcITPu0 (ORCPT ); Tue, 20 Sep 2016 11:50:26 -0400 Received: from mga02.intel.com ([134.134.136.20]:29440 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932124AbcITPuZ (ORCPT ); Tue, 20 Sep 2016 11:50:25 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,368,1470726000"; d="scan'208";a="763759605" From: Alexander Shishkin To: Peter Zijlstra Cc: Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo , tglx@linutronix.de, Alexander Shishkin Subject: [PATCH 0/2] perf, bts: Make BTS exclusive again Date: Tue, 20 Sep 2016 18:48:09 +0300 Message-Id: <20160920154811.3255-1-alexander.shishkin@linux.intel.com> X-Mailer: git-send-email 2.9.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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