mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Dave Jones <davej@redhat.com>
Cc: Don Zickus <dzickus@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	nzimmer@sgi.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 14:20:17 -0700	[thread overview]
Message-ID: <1339449617.27188.5.camel@joe2Laptop> (raw)
In-Reply-To: <20120611211239.GA12721@redhat.com>

On Mon, 2012-06-11 at 17:12 -0400, Dave Jones wrote:
[]
> 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
[]
> diff --git 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);

That wouldn't work.

Every pr_<level> other than pr_cont will always be start a new line.

You want pr_cont for each of these other than the ... ones.

It'd be better too just to use 2 pr_info lines like:

	pr_info("... version: %d bit width: %d generic registers: %d\n",
		x86_pmu.version, x86_pmu.cntval_bits, x86_pmu.num_counters);
	pr_info("... value mask: %016Lx max period: %016Lx fixed-purpose events: %d event mask: %016Lx\n",
		x86_pmu.cntval_mask, x86_pmu.max_period,
		x86_pmu.num_counters_fixed, x86_pmu.intel_ctrl);


  reply	other threads:[~2012-06-11 21:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-11 20:04 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 [this message]
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=1339449617.27188.5.camel@joe2Laptop \
    --to=joe@perches.com \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=dzickus@redhat.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

all inboxes | Powered by JetHome®