From: Linda Knippers <linda.knippers@hp.com>
To: ethan zhao <ethan.zhao@oracle.com>, Linda Knippers <ljklists@gmail.com>
Cc: Dirk Brandewie <dirk.brandewie@gmail.com>,
viresh.kumar@linaro.org, rjw@rjwysocki.net, corbet@lwn.net,
dirk.j.brandewie@intel.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
ethan.kernel@gmail.com, joe.jin@oracle.com,
brian.maly@oracle.com
Subject: Re: [PATCH 1/3] intel_pstate: skip the driver if Sun server has ACPI _PPC method
Date: Mon, 24 Nov 2014 10:54:21 -0500 [thread overview]
Message-ID: <547354AD.3010609@hp.com> (raw)
In-Reply-To: <54728CC0.1030708@oracle.com>
On 11/23/2014 8:41 PM, ethan zhao wrote:
> Linda,
>
> On 2014/11/21 12:44, Linda Knippers wrote:
>>
>> On 11/20/2014 07:37 PM, ethan zhao wrote:
>>> Dirk,
>>>
>>> On 2014/11/21 0:50, Dirk Brandewie wrote:
>>>> On 11/19/2014 12:22 PM, Linda Knippers wrote:
>>>>> On 11/18/2014 3:37 AM, Ethan Zhao wrote:
>>>>>> Oracle Sun X86 servers have dynamic power capping capability that
>>>>>> works via
>>>>>> ACPI _PPC method etc, so skip loading this driver if Sun server has
>>>>>> ACPI _PPC
>>>>>> enabled.
>>>>>>
>>>>>> Signed-off-by: Ethan Zhao <ethan.zhao@oracle.com>
>>>>>> ---
>>>>>> drivers/cpufreq/intel_pstate.c | 20 ++++++++++++++++++++
>>>>>> 1 file changed, 20 insertions(+)
>>>>>>
>>>>>> diff --git a/drivers/cpufreq/intel_pstate.c
>>>>>> b/drivers/cpufreq/intel_pstate.c
>>>>>> index 27bb6d3..5498eb0 100644
>>>>>> --- a/drivers/cpufreq/intel_pstate.c
>>>>>> +++ b/drivers/cpufreq/intel_pstate.c
>>>>>> @@ -943,6 +943,21 @@ static bool intel_pstate_no_acpi_pss(void)
>>>>>> return true;
>>>>>> }
>>>>>>
>>>>>> +static bool intel_pstate_has_acpi_ppc(void)
>>>>>> +{
>>>>>> + int i;
>>>>>> +
>>>>>> + for_each_possible_cpu(i) {
>>>>>> + struct acpi_processor *pr = per_cpu(processors, i);
>>>>>> +
>>>>>> + if (!pr)
>>>>>> + continue;
>>>>>> + if (acpi_has_method(pr->handle, "_PPC"))
>>>>>> + return true;
>>>>>> + }
>>>>>> + return false;
>>>>>> +}
>>>>>> +
>>>>>> struct hw_vendor_info {
>>>>>> u16 valid;
>>>>>> char oem_id[ACPI_OEM_ID_SIZE];
>>>>>> @@ -952,6 +967,7 @@ struct hw_vendor_info {
>>>>>> /* Hardware vendor-specific info that has its own power management
>>>>>> modes */
>>>>>> static struct hw_vendor_info vendor_info[] = {
>>>>>> {1, "HP ", "ProLiant"},
>>>>>> + {1, "ORACLE", ""},
>>>>>> {0, "", ""},
>>>>>> };
>>>>>>
>>>>>> @@ -969,12 +985,16 @@ static bool
>>>>>> intel_pstate_platform_pwr_mgmt_exists(void)
>>>>>> !strncmp(hdr.oem_table_id, v_info->oem_table_id,
>>>>>> ACPI_OEM_TABLE_ID_SIZE) &&
>>>>>> intel_pstate_no_acpi_pss())
>>>>>> return true;
>>>>>> + if (!strncmp(hdr.oem_id, v_info->oem_id, ACPI_OEM_ID_SIZE) &&
>>>>>> + intel_pstate_has_acpi_ppc())
>>>>> We need try this on a few platforms to make sure this patch doesn't
>>>>> break the
>>>>> HP platforms that may or may not need this driver, depending on the
>>>>> BIOS settings.
>>>>>
>>>> It looks like HP systems would get swept up in this check too if they
>>>> have _PPC
>> Right. This patch breaks HP ProLiant platforms when they are
>> configured to have the OS do power management. In that case,
>> the firmware exposes _PPC information.
> Okay, got it, The HP ProLiant has an option in BIOS could be enabled to "OS
> PM", so
> will export _PSS, _PPC, and this patch break this case.
>
>>
>>> No , this patch checks the oem_id against 'ORACLE" first, will not
>>> affect other vendors even they have _PPC.
>> I don't think that's how your code works. This patch will match any
>> vendor that is in the table, not just "ORACLE".
> Will change patch to match the oem-id out of the loop, such as following , how
> about it ?
>
> static bool intel_pstate_platform_pwr_mgmt_exists(void)
> {
> struct acpi_table_header hdr;
> struct hw_vendor_info *v_info;
>
> if (acpi_disabled
> || ACPI_FAILURE(acpi_get_table_header(ACPI_SIG_FADT, 0, &hdr)))
> return false;
>
> for (v_info = vendor_info; v_info->valid; v_info++) {
> if (!strncmp(hdr.oem_id, v_info->oem_id, ACPI_OEM_ID_SIZE)
> && !strncmp(hdr.oem_table_id, v_info->oem_table_id,
> ACPI_OEM_TABLE_ID_SIZE)
> && intel_pstate_no_acpi_pss())
> return true;
> }
>
> if (!strncmp(hdr.oem_id, v_info[1]->oem_id, ACPI_OEM_ID_SIZE) &&
> intel_pstate_has_acpi_ppc())
I really don't think you want to hard code a 1 there.
I think you need to do what Dirk suggested, which is to expand the
hw_vendor_info structure to specify the check that needs to be done
for each entry. For a ProLiant, it would be to call intel_pstate_no_acpi_pss()
and for an Oracle box, it would be to call intel_pstate_has_acpi_ppc().
-- ljk
> return true;
>
> return false;
> }
>
>>>> What about extending the hw_vendor_info struct to include whether _PSS or
>>> Except refer to ACPI DSDT, I don't know how to fill such info.
>>>> _PPC should be done for the platform since it appears that oracle and HP
>>>> have implemented similar functionality using two different methods.
>>> Maybe Linda could answer this whether HP also has _PPC and should be
>>> wept out.
>>> But that doesn't happen with on the same box at the same time.
>> I don't know how an Oracle box works but on a ProLiant, customers can
>> choose to have platform power management or OS power management.
>> When the platform is managing the power, we don't provide the _PSS
>> information. Since our oem information is in the table and there is
>> no _PSS, the intel_pstate driver doesn't stay loaded. That's what we want.
>>
>> When the platform configured to have the OS do the power management,
>> the firmware has _PSS and _PPC and we want the intel_pstate driver,
>> That's what your patch breaks. With your patch, the driver won't
>> stay loaded because our platform is in the table and the check for
>> _PPC passes.
>>
>> How does an Oracle box work?
> Oracle Sun servers (X86) don't have the option in BIOS to change the PM mode
> to firmware/OS,
> The BIOS always has _PSS and _PPC exported to OS whatever 'soft power capping'
> or 'hard power capping' enabled
> in SP configuration web page. if the power policy violation happened, firmware
> will notify OS via SCI with the changed _PPC
> number.
>
> Thanks,
> Ethan
>>
>> -- ljk
>>
>>> Thanks,
>>> Ethan
>>>>
>>>>> I don't suppose you tested on a ProLiant too?
>>>>>
>>>>> -- ljk
>>>>>
>>>>>> + return true;
>>>>>> }
>>>>>>
>>>>>> return false;
>>>>>> }
>>>>>> #else /* CONFIG_ACPI not enabled */
>>>>>> static inline bool intel_pstate_platform_pwr_mgmt_exists(void) {
>>>>>> return false; }
>>>>>> +static inline bool intel_pstate_has_acpi_ppc(void) { return false; }
>>>>>> #endif /* CONFIG_ACPI */
>>>>>>
>>>>>> static int __init intel_pstate_init(void)
>>>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2014-11-24 15:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 8:36 [PATCH 0/3] intel_pstate: allow to be built as module and handle Sun server power capping Ethan Zhao
2014-11-18 8:37 ` [PATCH 1/3] intel_pstate: skip the driver if Sun server has ACPI _PPC method Ethan Zhao
2014-11-19 20:22 ` Linda Knippers
2014-11-20 0:52 ` ethan
2014-11-20 16:50 ` Dirk Brandewie
2014-11-21 0:37 ` ethan zhao
2014-11-21 4:44 ` Linda Knippers
2014-11-24 1:41 ` ethan zhao
2014-11-24 15:54 ` Linda Knippers [this message]
2014-11-25 0:33 ` ethan
2014-11-18 8:37 ` [PATCH 2/3] intel_pstate: allow driver to be built as a module Ethan Zhao
2014-11-18 20:36 ` Rafael J. Wysocki
2014-11-18 8:37 ` [PATCH 3/3] intel_pstate: add module and kernel command line parameter to ignore ACPI _PPC Ethan Zhao
2014-11-18 8:37 ` [PATCH 0/3] intel_pstate: allow to be built as module and handle Sun server power capping Ethan Zhao
2014-11-18 8:37 ` [PATCH 1/3] intel_pstate: skip the driver if Sun server has ACPI _PPC method Ethan Zhao
2014-11-19 14:59 ` Dirk Brandewie
2014-11-20 1:07 ` ethan
2014-11-18 8:37 ` [PATCH 2/3] intel_pstate: allow driver to be built as a module Ethan Zhao
2014-11-19 18:58 ` Kristen Carlson Accardi
2014-11-20 1:01 ` ethan
2014-11-18 8:37 ` [PATCH 3/3] intel_pstate: add module and kernel command line parameter to ignore ACPI _PPC Ethan Zhao
2014-11-19 19:05 ` Kristen Carlson Accardi
2014-11-20 0:57 ` ethan
2014-11-20 21:23 ` Kristen Carlson Accardi
2014-11-21 3:07 ` Ethan Zhao
2014-11-21 5:00 ` Linda Knippers
2014-11-24 1:56 ` ethan zhao
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=547354AD.3010609@hp.com \
--to=linda.knippers@hp.com \
--cc=brian.maly@oracle.com \
--cc=corbet@lwn.net \
--cc=dirk.brandewie@gmail.com \
--cc=dirk.j.brandewie@intel.com \
--cc=ethan.kernel@gmail.com \
--cc=ethan.zhao@oracle.com \
--cc=joe.jin@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ljklists@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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;
as well as URLs for NNTP newsgroup(s).