linux-kernel - Re: [PATCH] intel_pstate: Turn per cpu printk into pr

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Aug 2014 10:27:58 -0700
From:	Dirk Brandewie <dirk.brandewie@...il.com>
To:	Andi Kleen <andi@...stfloor.org>, rafael.j.wysocki@...el.com
CC:	dirk.j.brandewie@...el.com, linux-kernel@...r.kernel.org,
	Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH] intel_pstate: Turn per cpu printk into pr_debug

On 08/27/2014 10:17 AM, Andi Kleen wrote:
> From: Andi Kleen <ak@...ux.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 <ak@...ux.intel.com>

Acked-by: Dirk Brandewie <dirk.j.brandewie@...el.com>

> ---
>   drivers/cpufreq/intel_pstate.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c
> index c5eac94..17be734 100644
> --- a/drivers/cpufreq/intel_pstate.c
> +++ b/drivers/cpufreq/intel_pstate.c
> @@ -688,7 +688,7 @@ static int intel_pstate_init_cpu(unsigned int cpunum)
>
>   	add_timer_on(&cpu->timer, cpunum);
>
> -	pr_info("Intel pstate controlling: cpu %d\n", cpunum);
> +	pr_debug("Intel pstate controlling: cpu %d\n", cpunum);
>
>   	return 0;
>   }
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/