Re: [PATCH] Quieten hrtimer printk: "Switched to high resolutionmode .."

[Thomas Gleixner]

On Mon, 29 Oct 2007, Michael Ellerman wrote:

> Change the hrtimer printk "Switched to high resolution mode .." to
> be KERN_DEBUG, rather than KERN_INFO. If users need to see this they
> can pass "loglevel" or "debug" on the command line, or check dmesg.
> 
> Signed-off-by: Michael Ellerman <michael@xxxxxxxxxxxxxx>

Thanks, applied.

	tglx

> ---
> 
> Any objections? It gets a little repetitive, eg:
> 
> Switched to high resolution mode on CPU 0
> Switched to high resolution mode on CPU 17
> Switched to high resolution mode on CPU 10
> Switched to high resolution mode on CPU 2
> Switched to high resolution mode on CPU 7
> Switched to high resolution mode on CPU 11
> Switched to high resolution mode on CPU 3
> Switched to high resolution mode on CPU 8
> Switched to high resolution mode on CPU 12
> Switched to high resolution mode on CPU 1
> Switched to high resolution mode on CPU 4
> Switched to high resolution mode on CPU 5
> Switched to high resolution mode on CPU 13
> Switched to high resolution mode on CPU 14
> Switched to high resolution mode on CPU 15
> Switched to high resolution mode on CPU 9
> Switched to high resolution mode on CPU 6
> Switched to high resolution mode on CPU 16
> 
> cheers
> 
> 
>  kernel/hrtimer.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> index b6d2ff7..22a2514 100644
> --- a/kernel/hrtimer.c
> +++ b/kernel/hrtimer.c
> @@ -602,7 +602,7 @@ static int hrtimer_switch_to_hres(void)
>  	/* "Retrigger" the interrupt to get things going */
>  	retrigger_next_event(NULL);
>  	local_irq_restore(flags);
> -	printk(KERN_INFO "Switched to high resolution mode on CPU %d\n",
> +	printk(KERN_DEBUG "Switched to high resolution mode on CPU %d\n",
>  	       smp_processor_id());
>  	return 1;
>  }
> -- 
> 1.5.2.rc1.1884.g59b20
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/