mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Roland Dreier <rdreier@cisco.com>
Cc: Joe Perches <joe@perches.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hrtimer: Remove overly verbose "switch to high res mode" message
Date: Thu, 24 Sep 2009 22:42:09 -0400	[thread overview]
Message-ID: <16460.1253846529@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 24 Sep 2009 14:15:14 PDT." <adaws3oyrh9.fsf@cisco.com>

[-- Attachment #1: Type: text/plain, Size: 998 bytes --]

On Thu, 24 Sep 2009 14:15:14 PDT, Roland Dreier said:
> 
>  > > -	printk(KERN_DEBUG "Switched to high resolution mode on CPU %d\n",
>  > > -	       smp_processor_id());
>  > 
>  > Perhaps pr_debug instead?
>  > It gets compiled to nothing unless DEBUG is defined.
> 
> Dunno... is that kernel log message ever useful now?

There's 3 cases to consider:

1) Kernel built with CONFIG_HIGH_RES_TIMERS=n.  We get no message then.

2) We have high-res timers and it succeeded. We probably don't care if that's
the usual case, so lose the message in that case, just like we probably
don't need a message that we managed to fork off init.

3) We attempted to switch to high-res mode, and it *failed*. We already throw
the appropriate KERN_WARNING for that a few lines up.

And since we issue a message in the one case we *care* about, we can
determine that the *lack* of that KERN_WARNING means the switch went OK.

Thus, we don't need the message, as it doesn't *tell* us anything we didn't
already know.

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2009-09-25  2:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-23 22:35 [PATCH 2/2] x86: Reduce verbosity of "PAT enabled" kernel message Roland Dreier
2009-09-23 22:47 ` Roland Dreier
2009-09-24  9:38   ` Ingo Molnar
2009-09-24 21:07     ` [PATCH] hrtimer: Remove overly verbose "switch to high res mode" message Roland Dreier
2009-09-24 21:12       ` Joe Perches
2009-09-24 21:15         ` Roland Dreier
2009-09-24 21:20           ` Joe Perches
2009-09-25  2:42           ` Valdis.Kletnieks [this message]
2009-09-27  6:10       ` [tip:timers/urgent] " tip-bot for Roland Dreier
2009-09-24  9:37 ` [tip:x86/urgent] x86: Reduce verbosity of "PAT enabled" kernel message tip-bot for Roland Dreier

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=16460.1253846529@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rdreier@cisco.com \
    --cc=tglx@linutronix.de \
    /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®