Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp3135046imw; Mon, 18 Jul 2022 02:47:18 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tlVb3CLlT6U1AbUaJFKUuCq6E8GaQzwjqTg+wvj4NfZBaAp4pUPMbSNhlkedJTn1enAjcs X-Received: by 2002:a17:902:e547:b0:16c:1ee:262f with SMTP id n7-20020a170902e54700b0016c01ee262fmr28616532plf.130.1658137638192; Mon, 18 Jul 2022 02:47:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658137638; cv=none; d=google.com; s=arc-20160816; b=lFriwIsPdBcorzoKP170RqRpZBtkhNI2cKA+i046VJ0GDAleZOQbyRT0H/2v/LhI8a h4UirQ36TfHZ6f8GMA5MxRP4lNfTp8TsC2HCEbzMQ/DrAhpNJgTMJ2/GFuCgLVJxrE5r SyI2B/V/vlbloV9Cgl8VuO9/W0S8ZrNvgI/HcKMkpaED5RIDEYWrF3JmsqxXjmOIrQik byuCHTDxZKkEDilf9SRdlppg0tlsFNwpnR3amgSK2bP+UfeZacRZ3XnKo6e5G46tpfpy 3fM/0R1jdQydb1cIC3AkwvtFRHuf370fSk3yRLO+dFnY2Bp4dyeT6YIxGxD8XIVxFqgh Xlkw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:subject:user-agent:mime-version:date:message-id; bh=4YkVfOfyOC0IFgjzSSIev1iYs/0QWhiPZWELQqrBXW8=; b=uVlThMLMDro/wcIPQbWtWZf8dy/Btg7Q3hT8Q3y2krDrXyUbb/O6rvWyb1kQDrcpnN fjFm3o7nW+kGqdva+IVO+HFo4w7OhHSa6BPk7o5/TakPZkOpLzp6MKTJ1lP311wgOkFh AieO53HuuhyoGd69/PqEp7CkLPA2B6os8el+1gHK7hdWu4Y6p12RRHPcffhntSO8Q3cj nIZ/Yel89D9Vw9JWMJf+0iagaVuMxi1b5Wz+kguQcIBsKWIXb0I4BPqws20caI9CgX2S oTVqrD81TLLE//XJMxF9GyeE7NT/Uko7xZ5XBfM1j1gEVeBbrRzL+pEhezAetnKvDsXv dNgA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f17-20020a056a00229100b00525b292ccf0si16888043pfe.124.2022.07.18.02.47.02; Mon, 18 Jul 2022 02:47:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234157AbiGRJmO (ORCPT + 99 others); Mon, 18 Jul 2022 05:42:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35108 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234210AbiGRJmI (ORCPT ); Mon, 18 Jul 2022 05:42:08 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id CF4E112AC7 for ; Mon, 18 Jul 2022 02:42:06 -0700 (PDT) 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 1DB101042; Mon, 18 Jul 2022 02:42:07 -0700 (PDT) Received: from [10.57.44.129] (unknown [10.57.44.129]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2EC013F70D; Mon, 18 Jul 2022 02:42:05 -0700 (PDT) Message-ID: Date: Mon, 18 Jul 2022 10:42:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH v3] drivers/perf: arm_spe: Fix consistency of SYS_PMSCR_EL1.CX To: James Clark , Anshuman Khandual , linux-arm-kernel@lists.infradead.org Cc: german.gomez@arm.com, Will Deacon , Mark Rutland , Alexey Budankov , linux-kernel@vger.kernel.org References: <20220714061302.2715102-1-anshuman.khandual@arm.com> <9b2982f1-023a-3499-7e87-f00b5a689ae9@arm.com> From: Suzuki K Poulose In-Reply-To: <9b2982f1-023a-3499-7e87-f00b5a689ae9@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_HI,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi James On 18/07/2022 10:30, James Clark wrote: > > > On 14/07/2022 07:13, Anshuman Khandual wrote: >> The arm_spe_pmu driver will enable SYS_PMSCR_EL1.CX in order to add CONTEXT >> packets into the traces, if the owner of the perf event runs with required >> capabilities i.e CAP_PERFMON or CAP_SYS_ADMIN via perfmon_capable() helper. >> >> The value of this bit is computed in the arm_spe_event_to_pmscr() function >> but the check for capabilities happens in the pmu event init callback i.e >> arm_spe_pmu_event_init(). This suggests that the value of the CX bit should >> remain consistent for the duration of the perf session. >> >> However, the function arm_spe_event_to_pmscr() may be called later during >> the event start callback i.e arm_spe_pmu_start() when the "current" process >> is not the owner of the perf session, hence the CX bit setting is currently >> not consistent. >> >> One way to fix this, is by caching the required value of the CX bit during >> the initialization of the PMU event, so that it remains consistent for the >> duration of the session. It uses currently unused 'event->hw.flags' element >> to cache perfmon_capable() value, which can be referred during event start >> callback to compute SYS_PMSCR_EL1.CX. This ensures consistent availability >> of context packets in the trace as per event owner capabilities. >> >> Drop BIT(SYS_PMSCR_EL1_CX_SHIFT) check in arm_spe_pmu_event_init(), because >> now CX bit cannot be set in arm_spe_event_to_pmscr() with perfmon_capable() >> disabled. >> >> Cc: Will Deacon >> Cc: Mark Rutland >> Cc: Alexey Budankov >> Cc: linux-arm-kernel@lists.infradead.org >> Cc: linux-kernel@vger.kernel.org >> Fixes: cea7d0d4a59b ("drivers/perf: Open access for CAP_PERFMON privileged process") >> Reported-by: German Gomez >> Signed-off-by: Anshuman Khandual >> --- >> Changes in V3: >> >> - Moved set_spe_event_has_cx() before arm_spe_event_to_pmscr() >> - Reinstated perfmon_capable() back in arm_spe_pmu_event_init() >> - Dropped BIT(SYS_PMSCR_EL1_CX_SHIFT) check in arm_spe_pmu_event_init() >> - Updated the commit message >> >> Changes in V2: >> >> https://lore.kernel.org/all/20220713085925.2627533-1-anshuman.khandual@arm.com/ >> >> - Moved CONFIG_PID_IN_CONTEXTIDR config check inside the helper per Suzuki >> - Changed the comment per Suzuki >> - Renamed the helpers Per Suzuki >> - Added "Fixes: " tag per German >> >> Changes in V1: >> >> https://lore.kernel.org/all/20220712051404.2546851-1-anshuman.khandual@arm.com/ >> >> >> drivers/perf/arm_spe_pmu.c | 22 ++++++++++++++++++++-- >> 1 file changed, 20 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/perf/arm_spe_pmu.c b/drivers/perf/arm_spe_pmu.c >> index db670b265897..b65a7d9640e1 100644 >> --- a/drivers/perf/arm_spe_pmu.c >> +++ b/drivers/perf/arm_spe_pmu.c >> @@ -39,6 +39,24 @@ >> #include >> #include >> >> +/* >> + * Cache if the event is allowed to trace Context information. >> + * This allows us to perform the check, i.e, perfmon_capable(), >> + * in the context of the event owner, once, during the event_init(). >> + */ >> +#define SPE_PMU_HW_FLAGS_CX BIT(0) >> + >> +static void set_spe_event_has_cx(struct perf_event *event) >> +{ >> + if (IS_ENABLED(CONFIG_PID_IN_CONTEXTIDR) && perfmon_capable()) >> + event->hw.flags |= SPE_PMU_HW_FLAGS_CX; >> +} >> + >> +static bool get_spe_event_has_cx(struct perf_event *event) >> +{ >> + return !!(event->hw.flags & SPE_PMU_HW_FLAGS_CX); >> +} >> + >> #define ARM_SPE_BUF_PAD_BYTE 0 >> >> struct arm_spe_pmu_buf { >> @@ -272,7 +290,7 @@ static u64 arm_spe_event_to_pmscr(struct perf_event *event) >> if (!attr->exclude_kernel) >> reg |= BIT(SYS_PMSCR_EL1_E1SPE_SHIFT); >> >> - if (IS_ENABLED(CONFIG_PID_IN_CONTEXTIDR) && perfmon_capable()) >> + if (get_spe_event_has_cx(event)) >> reg |= BIT(SYS_PMSCR_EL1_CX_SHIFT); >> >> return reg; >> @@ -709,10 +727,10 @@ static int arm_spe_pmu_event_init(struct perf_event *event) >> !(spe_pmu->features & SPE_PMU_FEAT_FILT_LAT)) >> return -EOPNOTSUPP; >> >> + set_spe_event_has_cx(event); >> reg = arm_spe_event_to_pmscr(event); >> if (!perfmon_capable() && >> (reg & (BIT(SYS_PMSCR_EL1_PA_SHIFT) | >> - BIT(SYS_PMSCR_EL1_CX_SHIFT) | > > The first part of the change looks ok, but I'm not sure about this removal here. > > Doesn't this mean that if you ask for context data when opening the event > without permission you don't get an error returned any more? It just silently > ignores it. How do you ask for context data with SPE ? If there was a way, we don't need this caching. The CX bit is set unconditionally on perfmon_capable() and is not controlled by an attribute. Ideally it is better to switch to an attribute. But given that it was never there, I wonder if this would be a problem for the existing perf users ? > > That changes the semantics of the perf event open call and I don't see why that's > needed to fix the issue about only checking the permissions of the owning process. > At least it seems like a separate unrelated change. > > It's also worth noting that the value doesn't need to be cached, and another > one line solution is just to check the permissions of the owning process. This > avoids duplicating something that is already saved, will survive any future > refactors of the permissions system, and doesn't use up space in hw_flags: > > if (IS_ENABLED(CONFIG_PID_IN_CONTEXTIDR) && > (has_capability(event->owner, CAP_PERFMON) || has_capability(event->owner, CAP_SYS_ADMIN))) > { > reg |= BIT(SYS_PMSCR_EL1_CX_SHIFT); > } We don't use any bits in the hw_events for SPE. So using a bit for storing something doesn't seem to be a wasted effort. Any future refactors to the permission system would need to take care of the current users. So that argument is not valid in either case. Cheers Suzuki