mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, tsc: downgrade message for fast calibration failure
Date: Thu, 31 Jan 2013 10:11:35 +0100	[thread overview]
Message-ID: <1359623495.1345.98.camel@x61.thuisdomein> (raw)
In-Reply-To: <1348654189.1664.12.camel@x61.thuisdomein>

On Wed, 2012-09-26 at 12:09 +0200, Paul Bolle wrote:
> When fast calibration of the TSC fails an error is printed:
>     tsc: Fast TSC calibration failed
> 
> This message was printed at default level (ie, as a warning) before
> commit c767a54ba0657e52e6edaa97cbe0b0a8bf1c1655 ("x86/debug: Add
> KERN_<LEVEL> to bare printks, convert printks to pr_<level>"). But it is
> more appropriate to print it at informational level. If fast calibration
> fails that only means an alternative calibration strategy will be tried,
> and if that strategy also fails only a warning is printed. Besides,
> there's nothing one can really do after noticing a fast calibration
> failure.
> 
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>

What's the status of this patch? Did anyone (besides Joe) have a look at
it? (I'm fine with the wordsmithing Joe suggested, by the way.)

> 0) This is a rather verbose commit explanation. For trivialities like
> these I try to write a very short explanation. But here the verbosity is
> meant to obfuscate my complete ignorance of the (calibration of the)
> TSC.
> 
> 1) By the way, it's debatable whether this message should be printed at
> informational or at notice level. But the difference between KERN_NOTICE
> and KERN_INFO is too subtle for me. I even find the difference between
> KERN_ALERT and KERN_CRIT, and between KERN_ERR and KERN_WARNING a bit
> subtle. Are there guidelines for choosing between those levels?
> 
>  arch/x86/kernel/tsc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> index cfa5d4f..4f258ae 100644
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -374,7 +374,7 @@ static unsigned long quick_pit_calibrate(void)
>  			goto success;
>  		}
>  	}
> -	pr_err("Fast TSC calibration failed\n");
> +	pr_info("Fast TSC calibration failed\n");
>  	return 0;
>  
>  success:


Paul Bolle


      parent reply	other threads:[~2013-01-31  9:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-26 10:09 Paul Bolle
2012-09-26 11:20 ` Joe Perches
2013-01-31  9:11 ` Paul Bolle [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=1359623495.1345.98.camel@x61.thuisdomein \
    --to=pebolle@tiscali.nl \
    --cc=hpa@zytor.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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®