From: Greg KH <gregkh@linuxfoundation.org>
To: Quentin Perret <quentin.perret@arm.com>
Cc: rafael@kernel.org, peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
dietmar.eggemann@arm.com
Subject: Re: [PATCH v2] PM / EM: Expose the Energy Model in debugfs
Date: Tue, 22 Jan 2019 19:41:36 +0100 [thread overview]
Message-ID: <20190122184136.GD31777@kroah.com> (raw)
In-Reply-To: <20190122164247.19439-1-quentin.perret@arm.com>
On Tue, Jan 22, 2019 at 04:42:47PM +0000, Quentin Perret wrote:
> The recently introduced Energy Model (EM) framework manages power cost
> tables of CPUs. These tables are currently only visible from kernel
> space. However, in order to debug the behaviour of subsystems that use
> the EM (EAS for example), it is often required to know what the power
> costs are from userspace.
>
> For this reason, introduce under /sys/kernel/debug/energy_model a set of
> directories representing the performance domains of the system. Each
> performance domain contains a set of sub-directories representing the
> different capacity states (cs) and their attributes, as well as a file
> exposing the related CPUs.
>
> The resulting hierarchy is as follows on Arm juno r0 for example:
>
> /sys/kernel/debug/energy_model
> ├── pd0
> │ ├── cpus
> │ ├── cs:450000
> │ │ ├── cost
> │ │ ├── frequency
> │ │ └── power
> │ ├── cs:575000
> │ │ ├── cost
> │ │ ├── frequency
> │ │ └── power
> │ ├── cs:700000
> │ │ ├── cost
> │ │ ├── frequency
> │ │ └── power
> │ ├── cs:775000
> │ │ ├── cost
> │ │ ├── frequency
> │ │ └── power
> │ └── cs:850000
> │ ├── cost
> │ ├── frequency
> │ └── power
> └── pd1
> ├── cpus
> ├── cs:1100000
> │ ├── cost
> │ ├── frequency
> │ └── power
> ├── cs:450000
> │ ├── cost
> │ ├── frequency
> │ └── power
> ├── cs:625000
> │ ├── cost
> │ ├── frequency
> │ └── power
> ├── cs:800000
> │ ├── cost
> │ ├── frequency
> │ └── power
> └── cs:950000
> ├── cost
> ├── frequency
> └── power
>
> Signed-off-by: Quentin Perret <quentin.perret@arm.com>
>
> ---
>
> V2: removed check on return value of debugfs_create_* (Greg KH)
> ---
> kernel/power/energy_model.c | 57 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 57 insertions(+)
Reviewed-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
next prev parent reply other threads:[~2019-01-22 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 16:42 Quentin Perret
2019-01-22 18:41 ` Greg KH [this message]
2019-01-23 9:28 ` Quentin Perret
2019-01-24 10:45 ` Rafael J. Wysocki
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=20190122184136.GD31777@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quentin.perret@arm.com \
--cc=rafael@kernel.org \
/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
Powered by JetHome