From: Nathan Lynch <nathanl@linux.ibm.com>
To: "Gautham R. Shenoy" <ego@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>,
Tyrel Datwyler <tyreld@linux.ibm.com>
Subject: Re: [PATCH v2 5/5] Documentation: Document sysfs interfaces purr, spurr, idle_purr, idle_spurr
Date: Fri, 21 Feb 2020 10:55:07 -0600 [thread overview]
Message-ID: <87blprubh0.fsf@linux.ibm.com> (raw)
In-Reply-To: <1582262314-8319-6-git-send-email-ego@linux.vnet.ibm.com>
"Gautham R. Shenoy" <ego@linux.vnet.ibm.com> writes:
> diff --git a/Documentation/ABI/testing/sysfs-devices-system-cpu b/Documentation/ABI/testing/sysfs-devices-system-cpu
> index 2e0e3b4..799dc737a 100644
> --- a/Documentation/ABI/testing/sysfs-devices-system-cpu
> +++ b/Documentation/ABI/testing/sysfs-devices-system-cpu
> @@ -580,3 +580,42 @@ Description: Secure Virtual Machine
> If 1, it means the system is using the Protected Execution
> Facility in POWER9 and newer processors. i.e., it is a Secure
> Virtual Machine.
> +
> +What: /sys/devices/system/cpu/cpuX/purr
> +Date: Apr 2005
> +Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
> +Description: PURR ticks for this CPU since the system boot.
> +
> + The Processor Utilization Resources Register (PURR) is
> + a 64-bit counter which provides an estimate of the
> + resources used by the CPU thread. The contents of this
> + register increases monotonically. This sysfs interface
> + exposes the number of PURR ticks for cpuX.
> +
> +What: /sys/devices/system/cpu/cpuX/spurr
> +Date: Dec 2006
> +Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
> +Description: SPURR ticks for this CPU since the system boot.
> +
> + The Scaled Processor Utilization Resources Register
> + (SPURR) is a 64-bit counter that provides a frequency
> + invariant estimate of the resources used by the CPU
> + thread. The contents of this register increases
> + monotonically. This sysfs interface exposes the number
> + of SPURR ticks for cpuX.
> +
> +What: /sys/devices/system/cpu/cpuX/idle_purr
> +Date: Nov 2019
> +Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
> +Description: PURR ticks for cpuX when it was idle.
> +
> + This sysfs interface exposes the number of PURR ticks
> + for cpuX when it was idle.
> +
> +What: /sys/devices/system/cpu/cpuX/spurr
Copy-paste error? This should be:
/sys/devices/system/cpu/cpuX/idle_spurr
> +Date: Nov 2019
And I suppose Nov 2019 is no longer accurate.
> +Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
> +Description: SPURR ticks for cpuX when it was idle.
> +
> + This sysfs interface exposes the number of SPURR ticks
> + for cpuX when it was idle.
> --
> 1.9.4
next prev parent reply other threads:[~2020-02-21 16:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 5:18 [PATCH v2 0/5] Track and expose idle PURR and SPURR ticks Gautham R. Shenoy
2020-02-21 5:18 ` [PATCH v2 1/5] powerpc: Move idle_loop_prolog()/epilog() functions to header file Gautham R. Shenoy
2020-02-21 15:03 ` Nathan Lynch
2020-02-24 4:55 ` Gautham R Shenoy
2020-03-06 17:06 ` Nathan Lynch
2020-02-21 5:18 ` [PATCH v2 2/5] powerpc/idle: Add accessor function to always read latest idle PURR Gautham R. Shenoy
2020-02-21 5:18 ` [PATCH v2 3/5] powerpc/pseries: Account for SPURR ticks on idle CPUs Gautham R. Shenoy
2020-02-21 16:47 ` Nathan Lynch
2020-02-24 5:05 ` Gautham R Shenoy
2020-02-21 5:18 ` [PATCH v2 4/5] powerpc/sysfs: Show idle_purr and idle_spurr for every CPU Gautham R. Shenoy
2020-02-21 16:50 ` Nathan Lynch
2020-02-24 5:14 ` Gautham R Shenoy
2020-02-25 10:20 ` Naveen N. Rao
2020-03-06 17:03 ` Nathan Lynch
2020-03-06 17:35 ` Naveen N. Rao
2020-02-21 5:18 ` [PATCH v2 5/5] Documentation: Document sysfs interfaces purr, spurr, idle_purr, idle_spurr Gautham R. Shenoy
2020-02-21 16:55 ` Nathan Lynch [this message]
2020-02-24 5:15 ` Gautham R Shenoy
2020-02-24 4:17 ` [PATCH v2 0/5] Track and expose idle PURR and SPURR ticks Kamalesh Babulal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87blprubh0.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=ego@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tyreld@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).