Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp3493427ybl; Fri, 20 Dec 2019 10:12:10 -0800 (PST) X-Google-Smtp-Source: APXvYqwcLdYj9zoQ31s2A/px9AEl6wJK9O3id4Nn/ScWWijlFhgH6+lGT46OC+4ij4+GAG3f4MYD X-Received: by 2002:a05:6830:11c3:: with SMTP id v3mr17246650otq.74.1576865530734; Fri, 20 Dec 2019 10:12:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1576865530; cv=none; d=google.com; s=arc-20160816; b=ldXNLZr2JM41kU2lY0I+DYmTPKEgttD78mV/CQLJWGZ0bIuQpPJzp/NfrvRQeU68qr T1PZgwpHsDXBqq6w5GbLGG5ir/U+pip42NAInT+oJFd1NiH0ON7jY3hAWTJrTtGqW2KH ZCrrNvcJTqW44LOaKxuFh5KKunrOv/BEituKHd+LP80lZ/R5fziMZS3Fj07B0I9LcAhw UbqOgd+xcubZo03zxiQgYDf7RfEtCnwerzP0MZ8xvq0Lvy1o3bHYJqijPD75G1gsbOUV YTmQ+T3WOBBLgm2XuA7q4FTEwSkNkrWmkLN+ooWKKg2iaU0WRpU6Po7i/1hg1YkEqssP b2rg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=TcgBGhRrxT2ZI3viTtByIP8HnQ73mKzfF7ih++Hu2Go=; b=i/Y2T0UAgix9EwhEeIbiR1F9xxZPD2AXDtAJBIgT+9uicgufD2Y3lZ/n+ukqjvTqtJ Qk1RjnFO7H7aheqzCZoRugeSIOlabnYdfZNgsNMGiSMx5X4BODWar/0oLKNR4TtAhOIc ZpKPWdaCWj999CaFZku8xIlZlAAt3RgZOyqMp0bLP1NIQOwe6PEoPsq8B+Cd3WBQwZ7x bVqO25NWutczcNJ2K2tpkUcDb3bVAaQIJgyW0lVlfUqfeYGF8DRecU8Sf5r1VGZVpQ8x tEMgC4ZyLApu8VFondaX1wS9/nK5oRsY71uLtBry55DNjPiiOjo2+RFQ5lbKZxDf071v 4BRw== 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 j9si3605845otn.294.2019.12.20.10.11.58; Fri, 20 Dec 2019 10:12:10 -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 S1727524AbfLTSKE (ORCPT + 99 others); Fri, 20 Dec 2019 13:10:04 -0500 Received: from foss.arm.com ([217.140.110.172]:53916 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727404AbfLTSKE (ORCPT ); Fri, 20 Dec 2019 13:10:04 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id B45D61FB; Fri, 20 Dec 2019 10:10:03 -0800 (PST) Received: from lakrids.cambridge.arm.com (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7A1F73F67D; Fri, 20 Dec 2019 10:10:02 -0800 (PST) Date: Fri, 20 Dec 2019 18:10:00 +0000 From: Mark Rutland To: Andrew Murray Cc: Marc Zyngier , Catalin Marinas , Will Deacon , Sudeep Holla , kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 15/18] perf: arm_spe: Handle guest/host exclusion flags Message-ID: <20191220180959.GF25258@lakrids.cambridge.arm.com> References: <20191220143025.33853-1-andrew.murray@arm.com> <20191220143025.33853-16-andrew.murray@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191220143025.33853-16-andrew.murray@arm.com> User-Agent: Mutt/1.11.1+11 (2f07cb52) (2018-12-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Dec 20, 2019 at 02:30:22PM +0000, Andrew Murray wrote: > A side effect of supporting the SPE in guests is that we prevent the > host from collecting data whilst inside a guest thus creating a black-out > window. This occurs because instead of emulating the SPE, we share it > with our guests. We used to permit this; do we know if anyone is using it? Thanks, Mark. > Let's accurately describe our capabilities by using the perf exclude > flags to prevent !exclude_guest and exclude_host flags from being used. > > Signed-off-by: Andrew Murray > --- > drivers/perf/arm_spe_pmu.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/perf/arm_spe_pmu.c b/drivers/perf/arm_spe_pmu.c > index 2d24af4cfcab..3703dbf459de 100644 > --- a/drivers/perf/arm_spe_pmu.c > +++ b/drivers/perf/arm_spe_pmu.c > @@ -679,6 +679,9 @@ static int arm_spe_pmu_event_init(struct perf_event *event) > if (attr->exclude_idle) > return -EOPNOTSUPP; > > + if (!attr->exclude_guest || attr->exclude_host) > + return -EOPNOTSUPP; > + > /* > * Feedback-directed frequency throttling doesn't work when we > * have a buffer of samples. We'd need to manually count the > -- > 2.21.0 >