[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YNw76ZUUUG+qUyP2@kroah.com>
Date: Wed, 30 Jun 2021 11:39:53 +0200
From: Greg KH <gregkh@...uxfoundation.org>
To: kan.liang@...ux.intel.com
Cc: peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
linux-kernel@...r.kernel.org, eranian@...gle.com,
namhyung@...nel.org, jolsa@...hat.com, ak@...ux.intel.com,
yao.jin@...ux.intel.com
Subject: Re: [PATCH V3 2/6] perf/x86/intel/uncore: Add alias PMU name
On Tue, Jun 29, 2021 at 11:13:59AM -0700, kan.liang@...ux.intel.com wrote:
> From: Kan Liang <kan.liang@...ux.intel.com>
>
> 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 is named
> by the real PMU name, e.g., uncore_cha_0. The user scripts which work
> well with the old numeric name may not work anymore.
>
> Add a new attribute "alias" to indicate the old numeric name. The
> following userspace perf tool patch will handle both names. The user
> scripts should work properly with the updated perf tool.
>
> Signed-off-by: Kan Liang <kan.liang@...ux.intel.com>
> Cc: gregkh@...uxfoundation.org
> ---
> arch/x86/events/intel/uncore.c | 19 +++++++++++++------
> arch/x86/events/intel/uncore.h | 1 +
> arch/x86/events/intel/uncore_snbep.c | 28 +++++++++++++++++++++++++++-
> 3 files changed, 41 insertions(+), 7 deletions(-)
No Documentation/ABI/ update for your new sysfs file?
:(
Powered by blists - more mailing lists