mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Quieten hrtimer printk: "Switched to high resolution mode .."
Date: Mon, 29 Oct 2007 09:47:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0710290946540.3186@localhost.localdomain> (raw)
In-Reply-To: <ed0a9ee8c6bc2ac894924b24c22a221a07e66931.1193635831.git.michael@ellerman.id.au>

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@ellerman.id.au>

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
> 

      reply	other threads:[~2007-10-29  8:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-29  5:35 Michael Ellerman
2007-10-29  8:47 ` Thomas Gleixner [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=alpine.LFD.0.9999.0710290946540.3186@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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

all inboxes | Powered by JetHome®