From: Linda Knippers <linda.knippers@hpe.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
tony.luck@intel.com, bp@alien8.de, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com, lenb@kernel.org,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] acpi: Issue _OSC call for native thermal interrupt handling
Date: Fri, 18 Mar 2016 11:00:13 -0400 [thread overview]
Message-ID: <56EC17FD.5050104@hpe.com> (raw)
In-Reply-To: <1766653.m1W9bgBQpQ@vostro.rjw.lan>
On 3/17/2016 8:17 PM, Rafael J. Wysocki wrote:
<snip>
>>>>>>> This change introduces a new function
>>>>>>> acpi_early_processor_set_osc(),
>>>>>>> which walks acpi name space and finds acpi processor object and
>>>>>>> set capability via _OSC method to take over thermal LVT.
>>>>>> Does this change just affect Skylake platforms or all platforms?
>>>>> Any platform which has Intel ® Speed Shift Technology (aka HWP)
>>>>> feature present and enabled.
>>
>> Could this be an unexpected change in behavior for platforms
>> with HWP that don't have this bug, assuming they would look at
>> the _OSC CPPP bit? That's actually my main concern here.
>
> Do you have any specific platforms in mind or just in general?
It's just general right now but as more HWP server platforms come out,
it may become specific.
-- ljk
>
> Thanks,
> Rafael
>
prev parent reply other threads:[~2016-03-18 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 18:24 [PATCH v4] acpi: Issue _OSC call for native thermal interrupt handling Srinivas Pandruvada
2016-03-17 20:03 ` Linda Knippers
2016-03-17 20:36 ` Srinivas Pandruvada
2016-03-17 20:51 ` Linda Knippers
2016-03-17 21:12 ` Srinivas Pandruvada
2016-03-17 23:44 ` Linda Knippers
2016-03-18 0:17 ` Rafael J. Wysocki
2016-03-18 15:00 ` Linda Knippers [this message]
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=56EC17FD.5050104@hpe.com \
--to=linda.knippers@hpe.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.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