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 01933C433EF for ; Tue, 14 Dec 2021 12:39:43 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=EHCVDHesKU1Ejyxgrus2toEJr/4IQ9Z1KhyItiyV/WI=; b=eH6hgN7wRz6H2u f6Qvkb2qM8LyEh4oWjBm+TPqPAvMI3Ui01goFi/S4nd+A6bi5euLUGcoNFykYptSffTiJSXXLnPmT CNm2W6Yx0uBCMZv/o0dhMm3knZVSGmq5YJf7XwnO2+Gg5fTmyx48qCOBuXhyRuBNYLfCx/PwtNf6k DqKmAP+4Nw4cezOXfx/jkyMmKO5oq8Mp0fIJ2Erij0+qo2e6G74uBmgnJMg1tyLS+H/e7xG0fAOZx Qh0oW8J9PG7bTYR69s/nG/XN6HzXXaFWwcKsdNG3x18VCKXObaF4Q9uF5ev7IA/tp5TjjprJab0DY Vj/AEN14hMuT5K3dnZag==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mx73o-00DyWZ-AW; Tue, 14 Dec 2021 12:37:36 +0000 Received: from ams.source.kernel.org ([145.40.68.75]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mx70L-00DxQB-AB for linux-arm-kernel@lists.infradead.org; Tue, 14 Dec 2021 12:34:03 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id EC301B8191E; Tue, 14 Dec 2021 12:33:59 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 48ECDC34605; Tue, 14 Dec 2021 12:33:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1639485238; bh=4Cj68ob9pH+Z5mhyMlecsSJ6G0Zss5CgowXAX+wVjXg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=IL2PtO6r3UOSQzalyAKXza3qe92S0JssI/YyURvVOSUnLWxOfOoPnze53HFCf7gtj dkjnPkUehhr8aFS50F62DoOP0yJtUGnfJsLCoL+iulvYD1Yhk9R/8pAaYw6LByUPM8 R7LXzQjXVwtapKNx9uiIOZoTQV0oqYa4cjqQhCKXcQ3lCnANW8B37i2YWBQuwMXGb+ rfoLf2QnwyklA14B92+TFH1B/CmQf4PrpJXfg2+BEssxP3kT6dLyhRo0A6dcaMIBV8 BYopRjVEaqt6jRPQU9sn17N/T+oJQbzpvLjIwSV5cm7PuJ03GCugq47B1fG//MqTHZ vk/QevurkrpVg== Date: Tue, 14 Dec 2021 12:33:53 +0000 From: Will Deacon To: Thierry Reding Cc: Mark Rutland , Rob Herring , Jon Hunter , linux-tegra@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/3] arm64: perf: Support Denver and Carmel PMUs Message-ID: <20211214123353.GD14247@willie-the-truck> References: <20211207150746.444478-1-thierry.reding@gmail.com> <20211207150746.444478-2-thierry.reding@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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-20211214_043401_664032_030D3AEE X-CRM114-Status: GOOD ( 29.78 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Dec 08, 2021 at 03:36:02PM +0100, Thierry Reding wrote: > On Tue, Dec 07, 2021 at 04:03:25PM +0000, Mark Rutland wrote: > > On Tue, Dec 07, 2021 at 04:07:45PM +0100, Thierry Reding wrote: > > > From: Thierry Reding > > > > > > Add support for the NVIDIA Denver and Carmel PMUs using the generic > > > PMUv3 event map for now. > > > > > > Signed-off-by: Thierry Reding > > > --- > > > arch/arm64/kernel/perf_event.c | 14 ++++++++++++++ > > > 1 file changed, 14 insertions(+) > > > > > > diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c > > > index b4044469527e..8c8cf369c450 100644 > > > --- a/arch/arm64/kernel/perf_event.c > > > +++ b/arch/arm64/kernel/perf_event.c > > > @@ -1247,6 +1247,18 @@ static int armv8_vulcan_pmu_init(struct arm_pmu *cpu_pmu) > > > armv8_vulcan_map_event); > > > } > > > > > > +static int armv8_denver_pmu_init(struct arm_pmu *cpu_pmu) > > > +{ > > > + return armv8_pmu_init_nogroups(cpu_pmu, "armv8_nvidia_denver", > > > + armv8_pmuv3_map_event); > > > +} > > > + > > > +static int armv8_carmel_pmu_init(struct arm_pmu *cpu_pmu) > > > +{ > > > + return armv8_pmu_init_nogroups(cpu_pmu, "armv8_nvidia_carmel", > > > + armv8_pmuv3_map_event); > > > +} > > > + > > > static const struct of_device_id armv8_pmu_of_device_ids[] = { > > > {.compatible = "arm,armv8-pmuv3", .data = armv8_pmuv3_init}, > > > {.compatible = "arm,cortex-a34-pmu", .data = armv8_a34_pmu_init}, > > > @@ -1265,6 +1277,8 @@ static const struct of_device_id armv8_pmu_of_device_ids[] = { > > > {.compatible = "arm,neoverse-n1-pmu", .data = armv8_n1_pmu_init}, > > > {.compatible = "cavium,thunder-pmu", .data = armv8_thunder_pmu_init}, > > > {.compatible = "brcm,vulcan-pmu", .data = armv8_vulcan_pmu_init}, > > > + {.compatible = "nvidia,denver-pmu", .data = armv8_denver_pmu_init}, > > > + {.compatible = "nvidia,carmel-pmu", .data = armv8_carmel_pmu_init}, > > > > Super trivial nit, but could we please organise this alphabetically (i.e. with carmel first?) > > > > With that: > > > > Acked-by: Mark Rutland > > > > I see now that we messed up the order of "cavium,thunder-pmu" and > > "brcm,vulcan-pmu", but otherwise this is ordered, and it's be nice to keep it > > that way. I can fix the order of those two in a separate patch. > > I ordered this chronologically (Denver for Tegra186 and Carmel for > Tegra194), which seemed a bit more natural, but I can reorder this > alphabetically if you prefer. > > Would Will be the right person to pick this up or should I take it > through the Tegra tree and then ARM SoC? Sorry, I missed this somehow. I've got some perf patches pending already, so it would be easiest for me to take this one directly (and then I can apply Robin's stuff on top). Is that ok? Will _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel