linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: Sudeep Holla <sudeep.holla@arm.com>, linux-acpi@vger.kernel.org
Cc: rjw@rjwysocki.net, lenb@kernel.org,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Subject: Re: [PATCH v2] ACPI / Processor: add sysfs support for low power idle
Date: Mon, 31 Jul 2017 12:18:08 -0600	[thread overview]
Message-ID: <8beff6e7-e27c-0b44-6236-a95fcd5335d5@codeaurora.org> (raw)
In-Reply-To: <3212e387-9f7d-5bd9-4612-79dddc77b05f@arm.com>

Hi Sudeep,

On 7/31/2017 10:25 AM, Sudeep Holla wrote:
> Sorry for the delay, I initial thought having this ABI under testing is
> fine as I really don't want any *real* user space programs to depend on
> this for various reasons stated in earlier threads, e.g. h/w auto
> promotable states, accuracy of the stats, ..etc
<sorry for repeating this part>
These fields are optional, so if there is no reliable way to keep track of  stats, platform
can choose not to expose it. If a platform is exposing inaccurate stats via this ACPI
interface, it is breaking the spec.
> But from Documentation/ABI/README, I see
>
> testing/
> 	This directory documents interfaces that are felt to be stable,
> 	as the main development of this interface has been completed.
> 	The interface can be changed to add new features, but the
> 	current interface will not break by doing this, unless grave
> 	errors or security problems are found in them. User space
> 	programs can start to rely on these interfaces,...
>
> which makes me worry. Since the use for this is purely for debug or
> optimization purposes, I still prefer simple single file debugfs entry.
> I still can't digest the fact that reading single file is time consuming
> as we are not using this interface at runtime IIUC. i.e. statistic are
> collected and analyzed offline.
These fields has the same utility/use-cases as the usage & time fields in cpuidle sysfs,
but provides more granularity - idle stats for different levels hierarchy and accurate
idle stats for states that require platform co-ordination.

The argument for having a single sysfs file per node was that reading individual
files might get expensive to get a snapshot(not the other way around). But, that
argument was weak as we typically read these only in debug settings and not that
often during runtime. So, the summary_stats file was removed and went with one
value per file.

--
Thanks,
Prashanth

  reply	other threads:[~2017-07-31 18:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-13 17:48 [PATCH v2] ACPI / Processor: add sysfs support for low power idle Prashanth Prakash
2017-07-31 16:25 ` Sudeep Holla
2017-07-31 18:18   ` Prakash, Prashanth [this message]
2017-08-01  9:18     ` Sudeep Holla
2017-08-01 17:15       ` Prakash, Prashanth
2017-08-01 17:34         ` Sudeep Holla
2017-08-23 16:04           ` Prakash, Prashanth
2017-08-28 23:56             ` Rafael J. Wysocki
2017-08-31 17:30               ` Prakash, Prashanth

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=8beff6e7-e27c-0b44-6236-a95fcd5335d5@codeaurora.org \
    --to=pprakash@codeaurora.org \
    --cc=Lorenzo.Pieralisi@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=sudeep.holla@arm.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).