Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp303201pxj; Wed, 23 Jun 2021 22:52:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxBSMrzfgckFyr3cu1Hdpx1vzqyrM6ulgAMDOv14bEHmrbnxi+KmFYSB1pJZDGdwwXCAMg3 X-Received: by 2002:a17:906:a28e:: with SMTP id i14mr3481858ejz.395.1624513968882; Wed, 23 Jun 2021 22:52:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624513968; cv=none; d=google.com; s=arc-20160816; b=QnMtMnVdpPQoPEjEZEjnJLRbf1r7OSwFTf59lwCzp1Ns0vP6tGIOVstouLHbvutLsP 72+l53Xpr4/Vgi8yW+3a1E37nk0hKL6aYrQdY5dIUn48FS/IQnO0pl/r9d/9PGRymk0R RZMqaNKoGGx//AbxUweJ11zs9z4uT+39ThSpmyD2zx5V0rZwAp5HNjOj/44zhw768m1X ms537UY9WcH2oUCqVpug1/KOj7Xaqk0BDE3Q8r5SOsxPXj5Uh191kVAhxCD83XZtw05F h+oRlQMKyhVRtozxay9azdWHATdd7zt17nrsBcjhFZ8NdTAU6TL2/ng4w45IejvzOlDn UZUA== 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 :dkim-signature; bh=B3aup8EMBKEU89ainQFs3BfuV3Sem1fITz1JAMyRfd8=; b=bw+MTBFnEDqym0BQv5iZkIvYGZAdMvQukYQovat2ruJt78TxL1YzpdEwZ12e7Si8pc SyF80PYTkl27PKqj53KfoK9NsxxM3DkL3LGmacHMflQmoSolVmT16GTgz/+SX4NnCW/T tZ5EZ/F9BdSX5kDYCp08sf5UtMDnMR5HKN3dXC6pAF01JXoM1xQn0LK8vJ3JM26iByPk c96N3BoqTaWEcyYErRnNUKNvu9FnRjRq1TN6cvpsSUJ+cB92CWf4gP0FBwbV3ptSrCeB qdayOEtFUOJp+w4x5ysLJ5dR8W2mLU3px7h1K8wYFJA/NTOFiNAAPWiMfyPoktDEk5ii IV+w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=gmzQvprD; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="DHwoh/st"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bm20si74682ejb.81.2021.06.23.22.52.24; Wed, 23 Jun 2021 22:52:48 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm1 header.b=gmzQvprD; dkim=pass header.i=@messagingengine.com header.s=fm3 header.b="DHwoh/st"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230315AbhFXFu0 (ORCPT + 99 others); Thu, 24 Jun 2021 01:50:26 -0400 Received: from new1-smtp.messagingengine.com ([66.111.4.221]:38801 "EHLO new1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229448AbhFXFuZ (ORCPT ); Thu, 24 Jun 2021 01:50:25 -0400 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id CF720580504; Thu, 24 Jun 2021 01:48:06 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 24 Jun 2021 01:48:06 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm1; bh=B3aup8EMBKEU89ainQFs3BfuV3S em1fITz1JAMyRfd8=; b=gmzQvprDQPMgfl1vCbyF8iLzlervQaVPSr3DcX2Nmdi pBHEv4HZ9RU5H9jdBGh/rX7MkNaUbdsUeKlCBcxPfmYKo3KQVpCYBpbB2XyF0Dx0 jIcadd+JysCr0zxrnRCfHH7WWCTdQjGT6lgqNwjoTng6mPcJdpgIq7MArr1Mf4j1 gyFhkdQPaTfgDobkNt7LCidbCuGwzrcvs1X1oxIYCAxBGs+2gpVHbUzUvCl69BLk IIcrpuEiAxPbQAmJySalWewzOnCjsstLOD+7sb5OBKv7MKwvirzR82RHW22z1p1s hqJER9rgbjDtOF6UfH1pVJtg+nYkr6H9qVMPU/WWmlA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=B3aup8 EMBKEU89ainQFs3BfuV3Sem1fITz1JAMyRfd8=; b=DHwoh/stGJO2MbZq5JyF28 3LebTgUv1vau4n0QDiKKXh30khIWuUqBZRH6DTwcwz7Iwsj18BrQ0425MpwXJGSm u8UxTWVEuubc2IDK/jW5OvPkJtxRhcRFDRHxdenYG7oSIfCAMl8XVDXh/iPDmBFE rlFN+1n6W+miQxR1LCFvtrY+/IV3esja++YJqAhi4ti71sw1MlV0tm+u241Grvw6 rPyjw771cfbl5fTBPklAB3ITxlGtt6VKm4RbhIEUJHTKK8BinHeAjSDt+P7Bc7CN aPi2bdbTOiItiMRbnuPHoBqgg2w+ayoBW3tFidO7UVQlscZoYTI6zbxFeyhzlAZg == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeeggedgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepifhrvghgucfmjfcuoehgrhgvgheskhhrohgrhhdrtghomheq necuggftrfgrthhtvghrnhepveeuheejgfffgfeivddukedvkedtleelleeghfeljeeiue eggeevueduudekvdetnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepghhrvghgsehkrhhorghhrdgtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 24 Jun 2021 01:48:05 -0400 (EDT) Date: Thu, 24 Jun 2021 07:48:02 +0200 From: Greg KH To: kan.liang@linux.intel.com Cc: peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org, eranian@google.com, namhyung@kernel.org, acme@kernel.org, jolsa@redhat.com, ak@linux.intel.com Subject: Re: [PATCH 2/7] perf: Create a symlink for a PMU Message-ID: References: <1624497729-158864-1-git-send-email-kan.liang@linux.intel.com> <1624497729-158864-3-git-send-email-kan.liang@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1624497729-158864-3-git-send-email-kan.liang@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 23, 2021 at 06:22:04PM -0700, kan.liang@linux.intel.com wrote: > From: Kan Liang > > A perf PMU may have two PMU names. For example, Intel Sapphire Rapids > server supports the discovery mechanism. Without the platform-specific > support, an uncore PMU is named by a type ID plus a box ID, e.g., > uncore_type_0_0, because the real name of the uncore PMU cannot be > retrieved from the discovery table. With the platform-specific support > later, perf has the mapping information from a type ID to a specific > uncore unit. Just like the previous platforms, the uncore PMU will be > named by the real PMU name, e.g., uncore_cha_0. The user scripts which > work well with the old name may not work anymore. To avoid the issue, a > symlink should be created from the new to the old name. > > The perf PMU devices are created under /sys/bus/event_source/devices/. > The symlink should be created in the same directory to facilitate the > perf tool. > > Add a new variable, link_name, to store the new name of a PMU. Link it > to the old name if applies. Ah, here is the "new name". This needs to be documented. But first off, why is this symlink suddenly needed? What is so special about this new hardware that it breaks the existing model? thanks, greg k-h