From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 7AE09C2BD09 for ; Mon, 1 Jul 2024 13:52:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=xcKmwy1+i8D++6IIpd414cv3bjNZjy5oYtLcLDOUM8s=; b=ou3epDd8CZt/gS8XR9a01CO6n1 Daut21gn6HPDCZnak4wMIRQ2ICWW13KQu9UXHlbXgNhou4xC6u6eLRkmAaCeJBpkYbXqAewf0Cp+3 8wLX0jOB3/ugLa9g/1uyr7VOwhBKiTWEbzc86fLx74hw+l+TsQ2hBoxGWGK7xvUUVh53ZsOuj9bP4 if6iNtCts4NQgtKTJ3i51pwIQbELza8AZM4odQUt6IwpiSXjsKIv4lv3tjMMl6IicFDnGnKuYUG6A I6+azs4nk1VxsjSAvp5XTvtJ4lp2jr3m9q5KlpdZ6o0yzkXwQciQ/yZQMfEgVo5G/vufp2JeRfiU3 1rMN2VKQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sOHSN-00000003Zg4-1Vmp; Mon, 01 Jul 2024 13:52:35 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sOHSC-00000003Zd3-3kh3 for linux-arm-kernel@lists.infradead.org; Mon, 01 Jul 2024 13:52:26 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 19564612DB; Mon, 1 Jul 2024 13:52:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 166F3C116B1; Mon, 1 Jul 2024 13:52:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1719841943; bh=9oMe0zzAooHD779ju56VF3sNjUtqOksjJ2v3RCSlPZY=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=QkKnz8Mx4IFgeqCOxqdYy/HO2YOSEqV169/HMVTU2nA/QL8nq5cUM/LhvBQjescmH zCHh+7wgTbNXz5jKetAPn72ivN35ppJMm/lKAHjIlUhbzK1+FHpl7mZOXCgIa7KFOs l+npOy54MWI6MGpBxNaEifvHGAS8BreAs3O34Q4E2S116LwwxWbc6sp48p6ydViSsE CueSmmPL21Ajvlu8200LUqTyhFuMezX7pG5wnP2xBYNLPbO85XbXQfTWN5rCk1w+aK 38awLD+hqR9pNRdHIFxBlGhlZ5fpPZ5cq5QhAySrQuY0bjPlo56o2S+/7Dy3VQwEc1 cA9GB9f2PC/HA== Date: Mon, 1 Jul 2024 14:52:16 +0100 From: Will Deacon To: Marc Zyngier Cc: "Rob Herring (Arm)" , Russell King , Peter Zijlstra , Ingo Molnar , Arnaldo Carvalho de Melo , Namhyung Kim , Mark Rutland , Alexander Shishkin , Jiri Olsa , Ian Rogers , Adrian Hunter , Oliver Upton , James Morse , Suzuki K Poulose , Zenghui Yu , Catalin Marinas , James Clark , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, kvmarm@lists.linux.dev Subject: Re: [PATCH v2 06/12] perf: arm_pmu: Remove event index to counter remapping Message-ID: <20240701135216.GD2250@willie-the-truck> References: <20240626-arm-pmu-3-9-icntr-v2-0-c9784b4f4065@kernel.org> <20240626-arm-pmu-3-9-icntr-v2-6-c9784b4f4065@kernel.org> <86ikxuir2k.wl-maz@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86ikxuir2k.wl-maz@kernel.org> User-Agent: Mutt/1.10.1 (2018-07-13) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240701_065225_090936_ADFC3AC2 X-CRM114-Status: GOOD ( 29.07 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Thu, Jun 27, 2024 at 12:05:23PM +0100, Marc Zyngier wrote: > On Wed, 26 Jun 2024 23:32:30 +0100, > "Rob Herring (Arm)" wrote: > > > > Xscale and Armv6 PMUs defined the cycle counter at 0 and event counters > > starting at 1 and had 1:1 event index to counter numbering. On Armv7 and > > later, this changed the cycle counter to 31 and event counters start at > > 0. The drivers for Armv7 and PMUv3 kept the old event index numbering > > and introduced an event index to counter conversion. The conversion uses > > masking to convert from event index to a counter number. This operation > > relies on having at most 32 counters so that the cycle counter index 0 > > can be transformed to counter number 31. > > > > Armv9.4 adds support for an additional fixed function counter > > (instructions) which increases possible counters to more than 32, and > > the conversion won't work anymore as a simple subtract and mask. The > > primary reason for the translation (other than history) seems to be to > > have a contiguous mask of counters 0-N. Keeping that would result in > > more complicated index to counter conversions. Instead, store a mask of > > available counters rather than just number of events. That provides more > > information in addition to the number of events. > > > > No (intended) functional changes. > > > > Signed-off-by: Rob Herring (Arm) > > [...] > > > diff --git a/include/linux/perf/arm_pmu.h b/include/linux/perf/arm_pmu.h > > index b3b34f6670cf..e5d6d204beab 100644 > > --- a/include/linux/perf/arm_pmu.h > > +++ b/include/linux/perf/arm_pmu.h > > @@ -96,7 +96,7 @@ struct arm_pmu { > > void (*stop)(struct arm_pmu *); > > void (*reset)(void *); > > int (*map_event)(struct perf_event *event); > > - int num_events; > > + DECLARE_BITMAP(cntr_mask, ARMPMU_MAX_HWEVENTS); > > I'm slightly worried by this, as this size is never used, let alone > checked by the individual drivers. I can perfectly picture some new > (non-architectural) PMU driver having more counters than that, and > blindly setting bits outside of the allowed range. I tend to agree. > One way to make it a bit safer would be to add a helper replacing the > various bitmap_set() calls, and enforcing that we never overflow this > bitmap. Or perhaps wd could leave the 'num_events' field intact and allocate the new bitmap dynamically? Rob -- what do you prefer? I think the rest of the series is ready to go. Will