Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3809660imu; Mon, 7 Jan 2019 09:50:35 -0800 (PST) X-Google-Smtp-Source: AFSGD/WgamTBJbBzpWritZhEYpGR+Tfq9kWXRwx6qzKQZJnK6WVF7YyKk/bECSJNI90EHih5bm4V X-Received: by 2002:a62:b511:: with SMTP id y17mr64543867pfe.199.1546883435165; Mon, 07 Jan 2019 09:50:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1546883435; cv=none; d=google.com; s=arc-20160816; b=OizNyJRpxnPoLNIkExzURzZFgJQQ9sgYy6rmQoZ84SRuJVfaaa/1TixW3t75pILT0I zLaJpF8282TetaffnWQFbAnleRnMKGJtFKP45nr40LDToOmK1/1Hs2GGJqpR8zcaMxak Pl5dVL+uL2EYASoePnB64gDa+jcmEpPLDyda+Z0bcviqt389ygMhtKz09YDcOI9BfDd5 yVo4P/U+kFq+kmTKzj7ENCwjDdYLVsVVxpVJmF93HVRgAPwLXTlJ1jJTlMyxjYHapOdB pHOan96cgh1L7sH3QyEVJb+XMe6ceHzltBvXV3Khakt2FKD8M44343izIH6V2HHBGMLb /ZEg== 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=oj/xYWGFTBUBqPEgy+XdjgXXjS7NE/uZEv6L4aL1LGk=; b=kukWK2IJ/KMNgmaygM9UJS5Jf/gzp8yLXL9mYF/ItElHMmTbJrAkco966GuIgRX5ol FiZtSZAji55g3Yk8YOGv44eZsnVPFviUSiSdlfVnqHKvUUSO9x45iw6rIoOTWTYu22fa epAeRrWjypx+swIKSkaE1V7YOgWVuzYdbgbYuoA5KFznamRa+KY26UhG9RHsPpxWOiG2 wskobE7S0noVd2GlRLe3wralgdfBIodR2kdPUwPIBtD8LXyLgatLQNx/VfpaPKVhVwtS 4rjVynTTodnROhER1wn5xqjQ0okoOxRZpaYV3UrrxPEezeBR4s4kBdCaBgYNeRNRPcmg EJ0w== 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 p186si7208715pgp.37.2019.01.07.09.50.19; Mon, 07 Jan 2019 09:50:35 -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 S1730467AbfAGQ2B (ORCPT + 99 others); Mon, 7 Jan 2019 11:28:01 -0500 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:34206 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730428AbfAGQ2A (ORCPT ); Mon, 7 Jan 2019 11:28:00 -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 55A9C15AB; Mon, 7 Jan 2019 08:28:00 -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 D56A93F5A0; Mon, 7 Jan 2019 08:27:55 -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 04/13] alpha: perf/core: use PERF_PMU_CAP_NO_EXCLUDE Date: Mon, 7 Jan 2019 16:27:21 +0000 Message-Id: <1546878450-20341-5-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 As the Alpha PMU doesn't support context exclusion let's advertise the PERF_PMU_CAP_NO_EXCLUDE capability. This ensures that perf will prevent us from handling events where any exclusion flags are set. Let's also remove the now unnecessary check for exclusion flags. This change means that __hw_perf_event_init will now also indicate that it doesn't support exclude_host and exclude_guest and will now implicitly return -EINVAL instead of -EPERM. This is likely more desirable as -EPERM will result in a kernel.perf_event_paranoid related warning from the perf userspace utility. Signed-off-by: Andrew Murray --- arch/alpha/kernel/perf_event.c | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/arch/alpha/kernel/perf_event.c b/arch/alpha/kernel/perf_event.c index 5613aa37..4341ccf 100644 --- a/arch/alpha/kernel/perf_event.c +++ b/arch/alpha/kernel/perf_event.c @@ -630,12 +630,6 @@ static int __hw_perf_event_init(struct perf_event *event) return ev; } - /* The EV67 does not support mode exclusion */ - if (attr->exclude_kernel || attr->exclude_user - || attr->exclude_hv || attr->exclude_idle) { - return -EPERM; - } - /* * We place the event type in event_base here and leave calculation * of the codes to programme the PMU for alpha_pmu_enable() because @@ -771,6 +765,7 @@ static struct pmu pmu = { .start = alpha_pmu_start, .stop = alpha_pmu_stop, .read = alpha_pmu_read, + .capabilities = PERF_PMU_CAP_NO_EXCLUDE, }; -- 2.7.4