Received: by 2002:a05:6358:bb9e:b0:b9:5105:a5b4 with SMTP id df30csp245109rwb; Fri, 2 Sep 2022 13:25:48 -0700 (PDT) X-Google-Smtp-Source: AA6agR4gr3FBezNmPpLjIH8E93t5JZJdkvNSrNgg7lE0yW7ji6bgjiCJF1GJ4PpUMcsUlidYngEA X-Received: by 2002:a17:906:3bd2:b0:731:3f03:1697 with SMTP id v18-20020a1709063bd200b007313f031697mr29316468ejf.289.1662150347908; Fri, 02 Sep 2022 13:25:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662150347; cv=none; d=google.com; s=arc-20160816; b=y9R+7rfbagIHOmsxvD9ZBUqnV6ErWr6ceYOLDrz9lvf6GZZE8Ad3KAN8IPpARq8iR6 +9iztCioe9dT/9X3YcgTShW35vuwPDz4itySkWKhKX3I8kV73Sv642Z7bP+a1duWojhZ eqeeNzHDslLfT3UaWUDL3D4tVovhGR+xztO5jayHMq3OBPmQm5leaDKu1mqB4YSNI6Y4 tamYOnCrjKRqI7GcHrkHZGMTNBMmiL14BKdAFZUDqUSYWOD7CjBWWBVjZeAkdQ5ojJxf AlLOYAbbtWLB0GlNwD/6BKt/vC1A/CMh7nW958UP2Sh3pTfgKP3rB2algYEyNxN1YieG Xvpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=ZOPlcPq5mWW3/eltxZYssEpmgD+5urPZQ8Ni9Senxj4=; b=i8ew28pK1QysqxQH5rL35FyZEqIQFWWNoY9jm315jae4dGp7BWT8N4bN+SRk6j2E5c mJxDcal5Mm5Mk5TWMDkVEanqOGDRhe78MYblN8j7eRQxk1PnpHPbi2KJkZ5d4gygIg0V BJbblVIxwC0i3F3KBd94D2mglJ7z3dgdgIvFAJWb+NTXiAULuJddPfvjjIZKL7Qw8aj9 XPtWgm2PxeJrKwVHAAf+YvAVRVsuOdqkK09TVoMbx8K81bGcP8lbFeYxPXQH7LFS3hMd gn/6XaotCS3NKYu+FFDRDhw8SXgkUjEfjgAHuUGb1l2YXGvwiSxbA9IgOsr1RLJn/9VS V6/g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=oBWrJjJg; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id hd30-20020a170907969e00b007416e100f3dsi2746947ejc.986.2022.09.02.13.25.22; Fri, 02 Sep 2022 13:25:47 -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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=oBWrJjJg; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230273AbiIBT0B (ORCPT + 99 others); Fri, 2 Sep 2022 15:26:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44202 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229538AbiIBTZ7 (ORCPT ); Fri, 2 Sep 2022 15:25:59 -0400 Received: from sin.source.kernel.org (sin.source.kernel.org [IPv6:2604:1380:40e1:4800::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 221B21CFD3; Fri, 2 Sep 2022 12:25:58 -0700 (PDT) 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 sin.source.kernel.org (Postfix) with ESMTPS id 5DC21CE30C7; Fri, 2 Sep 2022 19:25:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 04E10C433C1; Fri, 2 Sep 2022 19:25:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1662146754; bh=OXshCiSi6O3h3plOqJ6wkUls2kJW/yXQDTlsExEXJM4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oBWrJjJgGcCxYju+mSj+YLLLLYmYnb2DHtSDcBsriTOVBRFpSrHXCRdg6huRhmo2O v7N5lxKS+DtwxXQ0lNQ8oL5WaM6icuXqVaqLnUiHFg+5wjo2uiymILQe+CtAfAx8cY 4ojqRx2WjCPLfGWA6RSWU7AAqIPU0H9DiNm+C1I+/PQjGW3MrTbadMa1bKDkMsSYOJ iO5VFPVX5OOniUcLse1J5VDQu4Q3jz1JRIZom2rlk9IJW/BIFyY63W6AZdRuOhG1Z5 AABB3sUen+CJ1zfW9f7I3AfdQiYtHoiQPHVBTuqTjUV1po+5fkOGi5cDTxre3ohCpq 0BRKf3TbrrGoQ== Received: by quaco.ghostprotocols.net (Postfix, from userid 1000) id AA4CB404A1; Fri, 2 Sep 2022 16:25:51 -0300 (-03) Date: Fri, 2 Sep 2022 16:25:51 -0300 From: Arnaldo Carvalho de Melo To: Nick Forrington Cc: John Garry , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Will Deacon , James Clark , Mike Leach , Leo Yan , Mark Rutland , Alexander Shishkin , Jiri Olsa , Namhyung Kim , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH] perf vendor events: Add missing Neoverse V1 events Message-ID: References: <20220901151804.294823-1-nick.forrington@arm.com> <6813a737-736d-7e15-a44f-d800ed9248be@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6813a737-736d-7e15-a44f-d800ed9248be@arm.com> X-Url: http://acmel.wordpress.com X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Em Fri, Sep 02, 2022 at 03:12:49PM +0100, Nick Forrington escreveu: > On 02/09/2022 09:04, John Garry wrote: > > On 01/09/2022 16:18, Nick Forrington wrote: > > > Based on updated data from: > > > https://github.com/ARM-software/data/blob/master/pmu/neoverse-v1.json > > > > > > which is based on PMU event descriptions from the Arm Neoverse V1 > > > Technical Reference Manual. > > > > > > This adds the following missing events: > > > ASE_INST_SPEC > > > SVE_INST_SPEC > > > SVE_PRED_SPEC > > > SVE_PRED_EMPTY_SPEC > > > SVE_PRED_FULL_SPEC > > > SVE_PRED_PARTIAL_SPEC > > > SVE_LDFF_SPEC > > > SVE_LDFF_FAULT_SPEC > > > FP_SCALE_OPS_SPEC > > > FP_FIXED_OPS_SPEC > > > > > > It also moves REMOTE_ACCESS from other.json to memory.json. > > > > Any specific reason why? I see that neoverse n2 and a76-n1 still use > > "other" json for REMOTE_ACCESS. Nicer to be consistent. > > Thanks John, I agree on consistency. > > I think memory is a better categorisation (for all CPUs), and this is > consistent with what I submitted for various Cortex CPUs a while back. Were those patches processed or is some still outstanding? > I'd be happy to remove the REMOTE_ACCESS change here and update (or not) > REMOTE_ACCESS for Neoverse separately. > > > > > > > > > Signed-off-by: Nick Forrington > > > --- > > > > Apart from above: > > Reviewed-by: John Garry > Thanks, Nick So, how should we proceed? - Arnaldo