public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Don Zickus <dzickus@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	nzimmer@sgi.com, joe@perches.com, Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v3] watchdog: Quiet down the boot messages
Date: Mon, 11 Jun 2012 17:12:39 -0400	[thread overview]
Message-ID: <20120611211239.GA12721@redhat.com> (raw)
In-Reply-To: <1339445050-29941-1-git-send-email-dzickus@redhat.com>

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.

untested, but something like the below patch..

	Dave


diff --git a/arch/x86/kernel/cpu/perf_event.c b/arch/x86/kernel/cpu/perf_event.c
index c4706cf..68e83ad 100644
--- a/arch/x86/kernel/cpu/perf_event.c
+++ b/arch/x86/kernel/cpu/perf_event.c
@@ -1389,13 +1389,13 @@ static int __init init_hw_perf_events(void)
 	x86_pmu.attr_rdpmc = 1; /* enable userspace RDPMC usage by default */
 	x86_pmu_format_group.attrs = x86_pmu.format_attrs;
 
-	pr_info("... version:                %d\n",     x86_pmu.version);
-	pr_info("... bit width:              %d\n",     x86_pmu.cntval_bits);
-	pr_info("... generic registers:      %d\n",     x86_pmu.num_counters);
-	pr_info("... value mask:             %016Lx\n", x86_pmu.cntval_mask);
-	pr_info("... max period:             %016Lx\n", x86_pmu.max_period);
-	pr_info("... fixed-purpose events:   %d\n",     x86_pmu.num_counters_fixed);
-	pr_info("... event mask:             %016Lx\n", x86_pmu.intel_ctrl);
+	pr_info("... version: %d ", x86_pmu.version);
+	pr_info("bit width: %d ", x86_pmu.cntval_bits);
+	pr_info("generic registers: %d\n", x86_pmu.num_counters);
+	pr_info("... value mask: %016Lx ", x86_pmu.cntval_mask);
+	pr_info("max period: %016Lx ", x86_pmu.max_period);
+	pr_info("fixed-purpose events: %d ", x86_pmu.num_counters_fixed);
+	pr_info("event mask: %016Lx\n", x86_pmu.intel_ctrl);
 
 	perf_pmu_register(&pmu, "cpu", PERF_TYPE_RAW);
 	perf_cpu_notifier(x86_pmu_notifier);

  parent reply	other threads:[~2012-06-11 21:12 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 [this message]
2012-06-11 21:20   ` Joe Perches
2012-06-13  7:56   ` Ingo Molnar

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=20120611211239.GA12721@redhat.com \
    --to=davej@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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