From: Sudeep Holla <sudeep.holla@arm.com>
To: Hanjun Guo <hanjun.guo@linaro.org>,
Ashwin Chaugule <ashwin.chaugule@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux acpi <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
"ahs3@redhat.com" <ahs3@redhat.com>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>
Subject: Re: [PATCH RFC 2/5] ACPI / processor: always compile perflib if CONFIG_ACPI_PROCESSOR
Date: Fri, 08 May 2015 11:06:26 +0100 [thread overview]
Message-ID: <554C8AA2.8020105@arm.com> (raw)
In-Reply-To: <554C7960.4040107@linaro.org>
On 08/05/15 09:52, Hanjun Guo wrote:
> On 2015年05月07日 02:36, Ashwin Chaugule wrote:
>> Hello,
>>
>> On 6 May 2015 at 10:31, Sudeep Holla <sudeep.holla@arm.com> wrote:
>>> Similar to the idle, thermal and throttling libraries, always compile
>>> the perflib if CONFIG_ACPI_PROCESSOR is enabled. This not only makes
>>> perflib alligned with other libraries but also helps in some sanity
>>> testing of these ACPI methods even when a particular feature is not
>>> enabled in the kernel configuration.
>>>
>>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>>> ---
>>> drivers/acpi/Makefile | 2 +-
>>> include/acpi/processor.h | 29 -----------------------------
>>> include/linux/cpufreq.h | 4 ++++
>>> 3 files changed, 5 insertions(+), 30 deletions(-)
>>>
>>> diff --git a/drivers/acpi/Makefile b/drivers/acpi/Makefile
>>> index 8a063e276530..33aef9d8b260 100644
>>> --- a/drivers/acpi/Makefile
>>> +++ b/drivers/acpi/Makefile
>>> @@ -84,7 +84,7 @@ obj-$(CONFIG_ACPI_BGRT) += bgrt.o
>>> # processor has its own "processor." module_param namespace
>>> processor-y := processor_driver.o processor_throttling.o
>>> processor-y += processor_idle.o processor_thermal.o
>>> -processor-$(CONFIG_CPU_FREQ) += processor_perflib.o
>>> +processor-y += processor_perflib.o
>>
>> I'd prefer that we create a separate kconfig option for this. (perhaps
>> even default it to 'y'). This library is quite specific to a certain
>> type of CPU performance management methods (includes _PSS and friends)
>> which are superseded by CPPC. The OS is not expected to support both
>> at runtime, so by keeping this a config option, we can then disable it
>> at compile time when CPPC is enabled. We could couple
>
> I agree. CPPC and _PSS are different way of controlling CPU freq,
> and I think _PSS may not be used on ARM.
>
While I agree having a separate config option is good, but I won't
assume _PSS might not be used on ARM as I have seen patches posted on
the list in past to use _PSS on ARM platform[1].
Regards,
Sudeep
[1] http://marc.info/?l=linaro-acpi&m=139745485418399&w=2
next prev parent reply other threads:[~2015-05-08 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-06 14:31 [PATCH RFC 0/5] ACPI / core : few cleanups and updates for LPI Sudeep Holla
2015-05-06 14:31 ` [PATCH RFC 1/5] ACPI / containers : add support for ACPI0010 processor container Sudeep Holla
2015-05-08 8:50 ` Hanjun Guo
2015-05-08 14:06 ` Rafael J. Wysocki
2015-05-08 15:32 ` Sudeep Holla
2015-05-08 20:33 ` Rafael J. Wysocki
2015-05-06 14:31 ` [PATCH RFC 2/5] ACPI / processor: always compile perflib if CONFIG_ACPI_PROCESSOR Sudeep Holla
2015-05-06 18:36 ` Ashwin Chaugule
2015-05-08 8:52 ` Hanjun Guo
2015-05-08 10:06 ` Sudeep Holla [this message]
2015-05-06 14:31 ` [PATCH RFC 3/5] ACPI / sleep: move acpi_processor_sleep to sleep.c Sudeep Holla
2015-05-06 14:31 ` [PATCH RFC 4/5] ACPI / processor_idle: replace PREFIX with pr_fmt Sudeep Holla
2015-05-06 14:31 ` [PATCH RFC 5/5] ACPI / processor_idle : introduce ARCH_SUPPORTS_ACPI_PROCESSOR_CSTATE Sudeep Holla
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=554C8AA2.8020105@arm.com \
--to=sudeep.holla@arm.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=ahs3@redhat.com \
--cc=ashwin.chaugule@linaro.org \
--cc=hanjun.guo@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.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;
as well as URLs for NNTP newsgroup(s).