public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Dave Jones <davej@redhat.com>, Don Zickus <dzickus@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	nzimmer@sgi.com, joe@perches.com,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH v3] watchdog: Quiet down the boot messages
Date: Wed, 13 Jun 2012 09:56:37 +0200	[thread overview]
Message-ID: <20120613075637.GA18819@gmail.com> (raw)
In-Reply-To: <20120611211239.GA12721@redhat.com>


* Dave Jones <davej@redhat.com> wrote:

> On Mon, Jun 11, 2012 at 04:04:10PM -0400, Don Zickus wrote:
>  > A bunch of bugzillas have complained how noisy the nmi_watchdog is during
>  > boot-up especially with its expected failure cases (like virt and bios
>  > resource contention).
>  > 
>  > This is my attempt to quiet them down and keep it less confusing for the end
>  > user.  What I did is print the message for cpu0 and save it for future
>  > comparisons.  If future cpus have an identical message as cpu0, then don't
>  > print the redundant info.  However, if a future cpu has a different message,
>  > happily print that loudly.
> 
> Would anyone object to compressing these lines too ?
>  
>  >     ... version:                2
>  >     ... bit width:              40
>  >     ... generic registers:      2
>  >     ... value mask:             000000ffffffffff
>  >     ... max period:             000000007fffffff
>  >     ... fixed-purpose events:   3
>  >     ... event mask:             0000000700000003
> 
> That's a lot of wasted space, that could just as easily take 
> up two lines without losing readability.

Yeah, we can do that, this was early debug code.

I'd suggest compressing it further, to a single line, to 
something like:

 ... ver: 2, regs: 2/3, bits: 40, masks: 0xffffffffff/0x700000003/0x7fffffff

Thanks,

	Ingo

      parent reply	other threads:[~2012-06-13  7:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 20:04 [PATCH v3] watchdog: Quiet down the boot messages Don Zickus
2012-06-11 20:56 ` Joe Perches
2012-06-11 21:01   ` Don Zickus
2012-06-11 21:12 ` Dave Jones
2012-06-11 21:20   ` Joe Perches
2012-06-13  7:56   ` Ingo Molnar [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=20120613075637.GA18819@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nzimmer@sgi.com \
    /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