linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Preeti U Murthy <preeti@linux.vnet.ibm.com>
To: tglx@linutronix.de, mingo@kernel.org
Cc: peterz@infradead.org, linuxppc-dev@ozlabs.org,
	john.stultz@linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tick-broadcast: Fix the printing of broadcast masks
Date: Mon, 04 May 2015 11:21:28 +0530	[thread overview]
Message-ID: <554708E0.1010600@linux.vnet.ibm.com> (raw)
In-Reply-To: <20150428084520.3314.62668.stgit@preeti.in.ibm.com>

Ping.

Any comments on this patch ?

Regards
Preeti U Murthy
On 04/28/2015 02:15 PM, Preeti U Murthy wrote:
> Today the number of bits of the broadcast masks that is output into
> /proc/timer_list is sizeof(unsigned long). This means that on machines
> with larger number of CPUs, the bitmasks of CPUs beyond this range do
> not appear.
> 
> Fix this by using bitmap printing through "%*pb" instead, so as to
> output the broadcast masks for the range of nr_cpu_ids into
> /proc/timer_list.
> 
> Signed-off-by: Preeti U Murthy <preeti@linux.vnet.ibm.com>
> ---
> 
>  kernel/time/timer_list.c |    8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/kernel/time/timer_list.c b/kernel/time/timer_list.c
> index c82b03c..1afc726 100644
> --- a/kernel/time/timer_list.c
> +++ b/kernel/time/timer_list.c
> @@ -269,11 +269,11 @@ static void timer_list_show_tickdevices_header(struct seq_file *m)
>  {
>  #ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
>  	print_tickdevice(m, tick_get_broadcast_device(), -1);
> -	SEQ_printf(m, "tick_broadcast_mask: %08lx\n",
> -		   cpumask_bits(tick_get_broadcast_mask())[0]);
> +	SEQ_printf(m, "tick_broadcast_mask: %*pb\n",
> +		   cpumask_pr_args(tick_get_broadcast_mask()));
>  #ifdef CONFIG_TICK_ONESHOT
> -	SEQ_printf(m, "tick_broadcast_oneshot_mask: %08lx\n",
> -		   cpumask_bits(tick_get_broadcast_oneshot_mask())[0]);
> +	SEQ_printf(m, "tick_broadcast_oneshot_mask: %*pb\n",
> +		   cpumask_pr_args(tick_get_broadcast_oneshot_mask()));
>  #endif
>  	SEQ_printf(m, "\n");
>  #endif
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
> 

  reply	other threads:[~2015-05-04  5:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28  8:45 [PATCH] tick-broadcast: Fix the printing of broadcast masks Preeti U Murthy
2015-05-04  5:51 ` Preeti U Murthy [this message]
2015-05-13 23:40   ` John Stultz

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=554708E0.1010600@linux.vnet.ibm.com \
    --to=preeti@linux.vnet.ibm.com \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).