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 X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CF821C433F5 for ; Wed, 8 Sep 2021 01:04:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AD51F60F43 for ; Wed, 8 Sep 2021 01:04:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346382AbhIHBFH (ORCPT ); Tue, 7 Sep 2021 21:05:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47046 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239456AbhIHBFG (ORCPT ); Tue, 7 Sep 2021 21:05:06 -0400 Received: from mail-pl1-x630.google.com (mail-pl1-x630.google.com [IPv6:2607:f8b0:4864:20::630]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 674CDC061575 for ; Tue, 7 Sep 2021 18:03:59 -0700 (PDT) Received: by mail-pl1-x630.google.com with SMTP id e7so246053plh.8 for ; Tue, 07 Sep 2021 18:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0iKng76PsWyRz/8pjKL65aYQlih1TWo8dnb6KnDDehM=; b=gA2AKqSYLA1MsQE3BMExMBWz0L/kPrN0d88m681N9dDRm9y82WlVbC6+jWD0ghSlB2 SyFe6JEC96j2lU/x/FecVxc0WYkUZcUG9uoZpqzpweENWnSLhz5JKPTrGO9eCS27Vbvc ewatD2c1ew2eWWvkKyoX+9LBmuw46PIVIINoX6SHItS4Kk47q7OabMVfkxbBnPtll2SG Uqu7JK1N11ylCIyfv3MbaMrhirdiv3iPRTLfZIakN0PCojZw5OfR2W7zsOippo2Hb2UC XSBHw7iAga4VdN4tdA1JthLBERWT0L+AMeMHrii+pyS1jLW0BcEpe1VSAu9txz4ZfQZo Th3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0iKng76PsWyRz/8pjKL65aYQlih1TWo8dnb6KnDDehM=; b=Vh/izN9Mf5rkpEkjMOM/PEsJZaaaG8kZ+Fqh9e4tkmXSxRo7Q+lUrXZNV+vl2UcgSf IZ90/2P0nKng7AY6YVYNEwgeQ9Pn9kB+ZvIZkGMnFFQEe8LIIziSFG5V2d/AIDvmfPac To8+KCVKOTB4sDwb/sq1YPseA09IhlJimIb2GgJiNDhx9mQaOtmqRUui5wvgUsnZPYgi K7Xcs7glhitQ2gPlpxYb69meRktodfjpnQU1UgohSaIfwkXLuaRikSZTfvSxa2yMzanD sCQnET0IdKyxhZzStfejEFiNkRhjwrzlGaHlHViGu6nZfQY8DKtNAziIN1tIV5OtJUzO CTEQ== X-Gm-Message-State: AOAM531ih+Kjwgt0HpJBKpgbyjKef9XVGfEM6qe4dY2+k9XL7Wmy//MV wutK9TJHfyTZRLKDerUInkWUgFDpY+3r24nME4tulA== X-Google-Smtp-Source: ABdhPJyamM17dGx2IKarxEjJH/roNB9B0xLZUNSeDoP4i/s+QWcFqzVWNormFy+djtNq4zfCina5FNZQADngZlT7D84= X-Received: by 2002:a17:90b:3b84:: with SMTP id pc4mr1194364pjb.220.1631063038886; Tue, 07 Sep 2021 18:03:58 -0700 (PDT) MIME-Version: 1.0 References: <20210903050914.273525-1-kjain@linux.ibm.com> <20210903050914.273525-5-kjain@linux.ibm.com> In-Reply-To: <20210903050914.273525-5-kjain@linux.ibm.com> From: Dan Williams Date: Tue, 7 Sep 2021 18:03:48 -0700 Message-ID: Subject: Re: [RESEND PATCH v4 4/4] powerpc/papr_scm: Document papr_scm sysfs event format entries To: Kajol Jain Cc: Michael Ellerman , linuxppc-dev , Linux NVDIMM , Linux Kernel Mailing List , Peter Zijlstra , "Weiny, Ira" , Vishal L Verma , maddy@linux.ibm.com, Santosh Sivaraj , "Aneesh Kumar K.V" , Vaibhav Jain , atrajeev@linux.vnet.ibm.com, Thomas Gleixner , rnsastry@linux.ibm.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 2, 2021 at 10:11 PM Kajol Jain wrote: > > Details is added for the event, cpumask and format attributes > in the ABI documentation. > > Acked-by: Peter Zijlstra (Intel) > Reviewed-by: Madhavan Srinivasan > Tested-by: Nageswara R Sastry > Signed-off-by: Kajol Jain > --- > Documentation/ABI/testing/sysfs-bus-papr-pmem | 31 +++++++++++++++++++ > 1 file changed, 31 insertions(+) > > diff --git a/Documentation/ABI/testing/sysfs-bus-papr-pmem b/Documentation/ABI/testing/sysfs-bus-papr-pmem > index 95254cec92bf..4d86252448f8 100644 > --- a/Documentation/ABI/testing/sysfs-bus-papr-pmem > +++ b/Documentation/ABI/testing/sysfs-bus-papr-pmem > @@ -61,3 +61,34 @@ Description: > * "CchRHCnt" : Cache Read Hit Count > * "CchWHCnt" : Cache Write Hit Count > * "FastWCnt" : Fast Write Count > + > +What: /sys/devices/nmemX/format > +Date: June 2021 > +Contact: linuxppc-dev , nvdimm@lists.linux.dev, > +Description: (RO) Attribute group to describe the magic bits > + that go into perf_event_attr.config for a particular pmu. > + (See ABI/testing/sysfs-bus-event_source-devices-format). > + > + Each attribute under this group defines a bit range of the > + perf_event_attr.config. Supported attribute is listed > + below:: > + > + event = "config:0-4" - event ID > + > + For example:: > + noopstat = "event=0x1" > + > +What: /sys/devices/nmemX/events That's not a valid sysfs path. Did you mean /sys/bus/nd/devices/nmemX? > +Date: June 2021 > +Contact: linuxppc-dev , nvdimm@lists.linux.dev, > +Description: (RO) Attribute group to describe performance monitoring > + events specific to papr-scm. Each attribute in this group describes > + a single performance monitoring event supported by this nvdimm pmu. > + The name of the file is the name of the event. > + (See ABI/testing/sysfs-bus-event_source-devices-events). Given these events are in the generic namespace the ABI documentation should be generic as well. So I think move these entries to Documentation/ABI/testing/sysfs-bus-nvdimm directly. You can still mention papr-scm, but I would expect something like: What: /sys/bus/nd/devices/nmemX/events Date: September 2021 KernelVersion: 5.16 Contact: Kajol Jain Description: (RO) Attribute group to describe performance monitoring events for the nvdimm memory device. Each attribute in this group describes a single performance monitoring event supported by this nvdimm pmu. The name of the file is the name of the event. (See ABI/testing/sysfs-bus-event_source-devices-events). A listing of the events supported by a given nvdimm provider type can be found in Documentation/driver-api/nvdimm/$provider, for example: Documentation/driver-api/nvdimm/papr-scm. > + > +What: /sys/devices/nmemX/cpumask > +Date: June 2021 > +Contact: linuxppc-dev , nvdimm@lists.linux.dev, > +Description: (RO) This sysfs file exposes the cpumask which is designated to make > + HCALLs to retrieve nvdimm pmu event counter data. Seems this one would be provider generic, so no need to refer to PPC specific concepts like HCALLs.