On Tue, 2015-07-21 at 19:37 +0300, Konstantin Khlebnikov wrote:
> On 21.07.2015 18:37, Srinivas Pandruvada wrote:
> > On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
> >> On 21.07.2015 00:08, Srinivas Pandruvada wrote:
> >>> On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov
On 21.07.2015 18:37, Srinivas Pandruvada wrote:
On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
wrote:
On Thu,
On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
> On 21.07.2015 00:08, Srinivas Pandruvada wrote:
> > On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
> >> On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
> >> wrote:
> >>> On Thu, 2015-07-16 at 21:17 +0300,
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
wrote:
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is
On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
srinivas.pandruv...@linux.intel.com wrote:
On Thu,
On 21.07.2015 18:37, Srinivas Pandruvada wrote:
On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
On Tue, 2015-07-21 at 19:37 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 18:37, Srinivas Pandruvada wrote:
On Tue, 2015-07-21 at 13:25 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On 21.07.2015 00:08, Srinivas Pandruvada wrote:
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
srinivas.pandruv...@linux.intel.com wrote:
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
IPMI can control CPU
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
> On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
> wrote:
> > On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
> >> IPMI can control CPU P-states remotely: configuration is reported via
> >> common ACPI interface
On Fri, 2015-07-17 at 07:36 +0300, Konstantin Khlebnikov wrote:
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
srinivas.pandruv...@linux.intel.com wrote:
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported
On Fri, Jul 17, 2015 at 9:00 AM, ethan zhao wrote:
>
> On 2015/7/17 2:17, Konstantin Khlebnikov wrote:
>>
>> IPMI can control CPU P-states remotely: configuration is reported via
>> common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
>> support in intel_pstate to receive and
On 2015/7/17 2:17, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to receive and use these P-state limits.
* ignore limit of top state in _PPC: it
On 2015/7/17 2:17, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to receive and use these P-state limits.
* ignore limit of top state in _PPC: it
On Fri, Jul 17, 2015 at 9:00 AM, ethan zhao ethan.z...@oracle.com wrote:
On 2015/7/17 2:17, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
wrote:
> On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
>> IPMI can control CPU P-states remotely: configuration is reported via
>> common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
>> support in
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
> IPMI can control CPU P-states remotely: configuration is reported via
> common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
> support in intel_pstate to receive and use these P-state limits.
>
> * ignore limit
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to receive and use these P-state limits.
* ignore limit of top state in _PPC: it lower than turbo boost frequency
* register
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to receive and use these P-state limits.
* ignore limit of top state in _PPC: it lower than turbo boost frequency
* register
On Fri, Jul 17, 2015 at 1:08 AM, Srinivas Pandruvada
srinivas.pandruv...@linux.intel.com wrote:
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required
On Thu, 2015-07-16 at 21:17 +0300, Konstantin Khlebnikov wrote:
IPMI can control CPU P-states remotely: configuration is reported via
common ACPI interface (_PPC/_PSS/etc). This patch adds required minimal
support in intel_pstate to receive and use these P-state limits.
* ignore limit of top
20 matches
Mail list logo