On Wednesday, August 27, 2014 10:27:58 AM Dirk Brandewie wrote:
> On 08/27/2014 10:17 AM, Andi Kleen wrote:
> > From: Andi Kleen
> >
> > On larger systems intel_pstate currently spams the boot up
> > log with its "Intel pstate controlling ..." message for each CPU.
> > It's the only subsystem
On 08/27/2014 10:17 AM, Andi Kleen wrote:
From: Andi Kleen
On larger systems intel_pstate currently spams the boot up
log with its "Intel pstate controlling ..." message for each CPU.
It's the only subsystem that prints a message for each
CPU.
Turn the message into a pr_debug.
Signed-off-by:
From: Andi Kleen
On larger systems intel_pstate currently spams the boot up
log with its "Intel pstate controlling ..." message for each CPU.
It's the only subsystem that prints a message for each
CPU.
Turn the message into a pr_debug.
Signed-off-by: Andi Kleen
---
From: Andi Kleen a...@linux.intel.com
On larger systems intel_pstate currently spams the boot up
log with its Intel pstate controlling ... message for each CPU.
It's the only subsystem that prints a message for each
CPU.
Turn the message into a pr_debug.
Signed-off-by: Andi Kleen
On 08/27/2014 10:17 AM, Andi Kleen wrote:
From: Andi Kleen a...@linux.intel.com
On larger systems intel_pstate currently spams the boot up
log with its Intel pstate controlling ... message for each CPU.
It's the only subsystem that prints a message for each
CPU.
Turn the message into a
On Wednesday, August 27, 2014 10:27:58 AM Dirk Brandewie wrote:
On 08/27/2014 10:17 AM, Andi Kleen wrote:
From: Andi Kleen a...@linux.intel.com
On larger systems intel_pstate currently spams the boot up
log with its Intel pstate controlling ... message for each CPU.
It's the only
6 matches
Mail list logo
