From: "Prakash, Prashanth" <pprakash@codeaurora.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Al Stone <ahs3@redhat.com>
Cc: ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Alexey Klimov <alexey.klimov@arm.com>, Hoan Tran <hotran@apm.com>,
Christopher Covington <cov@codeaurora.org>
Subject: Re: [PATCH 0/2] additional sysfs entries for CPPC
Date: Fri, 3 Mar 2017 11:32:55 -0700 [thread overview]
Message-ID: <11d1f119-1dac-1045-cd86-14972982bb29@codeaurora.org> (raw)
In-Reply-To: <f09519cd-4399-5253-8e8d-30611a85b228@codeaurora.org>
Hi Rafael,
On 2/13/2017 9:38 AM, Prakash, Prashanth wrote:
[...]
>>> Tested-by: Al Stone <ahs3@redhat.com>
>> I'm not actually sure about the assumption this series is based on.
>>
>> I don't see anything in the spec to guarantee that it will always be
>> safe to evaluate _CPC only once and cache its output.
> Among the Performance capabilities registers(section 8.4.7.1.1), the only
> register that can change dynamically is Guaranteed performance register.
> We are not supporting/using Guaranteed performance at the moment.
>
> Guaranteed performance Register has an associated Notify event which will be
> invoked when it changes. No such events are associated with other capabilities
> register. Similar distinction is made in the beginning of section 8.4.7.1.1:
> "Figure 8-47 outlines the static performance thresholds of the platform
> and the dynamic guaranteed performance threshold."
>
> I agree spec isn't very clear about marking these registers as static except
> that one sentence I quoted above, but there is enough in spec to guarantee
> that the capabilities we are using will not change dynamically.
Does the above sound reasonable? Any other feedback on this patch set?
--
Thanks,
Prashanth
next prev parent reply other threads:[~2017-03-03 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-15 1:06 [PATCH 0/2] additional sysfs entries for CPPC Prashanth Prakash
2016-12-15 1:06 ` [PATCH 1/2] ACPI / CPPC: read all perf caps in a single cppc read command Prashanth Prakash
2016-12-15 1:06 ` [PATCH 2/2] ACPI / CPPC: add sysfs entries for CPPC perf capabilities Prashanth Prakash
2017-01-03 18:37 ` [PATCH 0/2] additional sysfs entries for CPPC Al Stone
2017-01-05 17:59 ` Prakash, Prashanth
2017-02-08 22:10 ` Al Stone
2017-02-09 0:44 ` Rafael J. Wysocki
2017-02-13 16:38 ` Prakash, Prashanth
2017-03-03 18:32 ` Prakash, Prashanth [this message]
2017-03-24 16:34 ` Prakash, Prashanth
2017-03-25 13:32 ` Rafael J. Wysocki
2017-03-27 17:00 ` 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=11d1f119-1dac-1045-cd86-14972982bb29@codeaurora.org \
--to=pprakash@codeaurora.org \
--cc=ahs3@redhat.com \
--cc=alexey.klimov@arm.com \
--cc=cov@codeaurora.org \
--cc=hotran@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
/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