Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3810521imu; Mon, 7 Jan 2019 09:51:34 -0800 (PST) X-Google-Smtp-Source: AFSGD/VwUPheCNBOyKuOAf+tg7sDSMM8vUMRGoNyyk2qEExahcncV/SJyyTndqoZyxC45fGu0RCv X-Received: by 2002:a62:de06:: with SMTP id h6mr65683173pfg.158.1546883494257; Mon, 07 Jan 2019 09:51:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546883494; cv=none; d=google.com; s=arc-20160816; b=r+702AAgeALLknS0hKRiWJPXqyP+34RFCf5yFYMcGRLqQUvvOvDWQydp1+o2kX9YrO b19MHqW4YOKpBfOODbxhQzZyaAty9c3vezBVWaZaNPcbSieE6FEwgAhcAj8VBoo2Ktr7 jBwZKsNABKPvhVRuUjYQUuHwBBoPalJhEdXdUbu7fSUjk5NPHU0samysjt2LgL3qMEyl G6s5/ngYb/8e6BDtqm+gq27M9EWRCIy1X6mqTd4zIf1UYEa6lOLC2VcVytnIPnD3TWO2 JHz3ynHnoEqvbw57lac4m11cSKNnaw5jcM9B85OTDJHN4pGuRbEL+wy+pyhbFvdsaikX vJ3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=UwTsKLUcDYhoMzYUkGVxyvxoHgkPOjCTVqwKvbr78xs=; b=R0vqM/3G9k6IPQn/aConGMMiChU9RYm1/cLvrP1jZ+w1OswY0ZEhuv+2BfdYMwH3nU PcbK82QhRj0eM1jtWfj4M0X1vU7H4DO3AxvZ/494sOgGujfg5M0mTE/e7YifKJwfaDV9 B7xQlSVPkfoy98OYDT+tUag8hM5lLLroEKgE6ZxnmYBX9rN1JvEnUr6gwv3hqazrdUHk j7aGHdg/lou1YnLSe189K9t5hHbAUuzzQNaLNhO5aMm1ZKjeVbxdLx+sIJtUIZ8j579n 0CwN7grvppZcIDBhUejtTBXXVvM4ddlHx8gul86dNdIvUttAUTm6Q80CkFOZ5eMzC4Co YtLw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l81si64258381pfj.230.2019.01.07.09.51.18; Mon, 07 Jan 2019 09:51:34 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730443AbfAGQ15 (ORCPT + 99 others); Mon, 7 Jan 2019 11:27:57 -0500 Received: from foss.arm.com ([217.140.101.70]:34166 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730428AbfAGQ14 (ORCPT ); Mon, 7 Jan 2019 11:27:56 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 89A251596; Mon, 7 Jan 2019 08:27:55 -0800 (PST) Received: from e119886-lin.cambridge.arm.com (unknown [10.37.6.11]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 119B53F5A0; Mon, 7 Jan 2019 08:27:50 -0800 (PST) From: Andrew Murray To: Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Richard Henderson , Ivan Kokshaysky , Matt Turner , Will Deacon , Mark Rutland , Shawn Guo , Sascha Hauer , Benjamin Herrenschmidt , Paul Mackerras , Thomas Gleixner , Borislav Petkov , Russell King , suzuki.poulose@arm.com, robin.murphy@arm.com, Michael Ellerman Cc: x86@kernel.org, linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-alpha@vger.kernel.org Subject: [PATCH v4 03/13] perf/core: add PERF_PMU_CAP_NO_EXCLUDE for exclusion incapable PMUs Date: Mon, 7 Jan 2019 16:27:20 +0000 Message-Id: <1546878450-20341-4-git-send-email-andrew.murray@arm.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1546878450-20341-1-git-send-email-andrew.murray@arm.com> References: <1546878450-20341-1-git-send-email-andrew.murray@arm.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Many PMU drivers do not have the capability to exclude counting events that occur in specific contexts such as idle, kernel, guest, etc. These drivers indicate this by returning an error in their event_init upon testing the events attribute flags. This approach is error prone and often inconsistent. Let's instead allow PMU drivers to advertise their inability to exclude based on context via a new capability: PERF_PMU_CAP_NO_EXCLUDE. This allows the perf core to reject requests for exclusion events where there is no support in the PMU. Signed-off-by: Andrew Murray --- include/linux/perf_event.h | 1 + kernel/events/core.c | 9 +++++++++ 2 files changed, 10 insertions(+) diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h index 54a78d2..cec02dc 100644 --- a/include/linux/perf_event.h +++ b/include/linux/perf_event.h @@ -244,6 +244,7 @@ struct perf_event; #define PERF_PMU_CAP_EXCLUSIVE 0x10 #define PERF_PMU_CAP_ITRACE 0x20 #define PERF_PMU_CAP_HETEROGENEOUS_CPUS 0x40 +#define PERF_PMU_CAP_NO_EXCLUDE 0x80 /** * struct pmu - generic performance monitoring unit diff --git a/kernel/events/core.c b/kernel/events/core.c index 3cd13a3..fbe59b7 100644 --- a/kernel/events/core.c +++ b/kernel/events/core.c @@ -9772,6 +9772,15 @@ static int perf_try_init_event(struct pmu *pmu, struct perf_event *event) if (ctx) perf_event_ctx_unlock(event->group_leader, ctx); + if (!ret) { + if (pmu->capabilities & PERF_PMU_CAP_NO_EXCLUDE && + event_has_any_exclude_flag(event)) { + if (event->destroy) + event->destroy(event); + ret = -EINVAL; + } + } + if (ret) module_put(pmu->module); -- 2.7.4