mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: hch@infradead.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (9/9): no timer interrupts in idle.
Date: Thu, 22 Apr 2004 03:28:23 +0530	[thread overview]
Message-ID: <20040421215823.GB5014@in.ibm.com> (raw)
In-Reply-To: <20040421185206.GB7781@mschwid3.boeblingen.de.ibm.com>

On Wed, Apr 21, 2004 at 08:52:06PM +0200, Martin Schwidefsky wrote:
> diff -urN linux-2.6/kernel/rcupdate.c linux-2.6-s390/kernel/rcupdate.c
> --- linux-2.6/kernel/rcupdate.c	Wed Apr 21 20:25:10 2004
> +++ linux-2.6-s390/kernel/rcupdate.c	Wed Apr 21 20:25:33 2004
> @@ -96,6 +96,10 @@
>  	}
>  }
>  
> +#ifndef __ARCH_HAS_IDLE_CPU_MASK
> +#define idle_cpu_mask CPU_MASK_NONE
> +#endif
> +
>  /*
>   * Register a new batch of callbacks, and start it up if there is currently no
>   * active batch and the batch to be registered has not already occurred.
> @@ -111,7 +115,10 @@
>  		return;
>  	}
>  	/* Can't change, since spin lock held. */
> -	rcu_ctrlblk.rcu_cpu_mask = cpu_online_map;
> +	rcu_ctrlblk.rcu_cpu_mask = idle_cpu_mask;
> +	cpus_complement(rcu_ctrlblk.rcu_cpu_mask);
> +	cpus_and(rcu_ctrlblk.rcu_cpu_mask, cpu_online_map,
> +		 rcu_ctrlblk.rcu_cpu_mask);
>  }

Defining idle_cpu_mask in the middle of RCU code is really not a good idea.
A cleaner solution would be to define idle_cpu_mask in sched.c
and initialize it to CPU_MASK_NONE there. You could put it in 
sched.h, but then there is the likelyhood of people using
idle_cpu_mask for things other than initialization in which
case NR_CPUS > 64 compilation will fail.

Thanks
Dipankar

  reply	other threads:[~2004-04-21 22:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 18:52 Martin Schwidefsky
2004-04-21 21:58 ` Dipankar Sarma [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-29  8:24 Martin Schwidefsky
2004-04-29 12:06 ` Dipankar Sarma
2004-04-29  7:43 Martin Schwidefsky
2004-04-29  8:16 ` Dipankar Sarma
2004-04-23  8:48 Martin Schwidefsky
2004-04-22 14:56 Martin Schwidefsky
2004-04-28 19:07 ` Dipankar Sarma
2004-04-22 12:44 Martin Schwidefsky
2004-04-22 13:11 ` Arjan van de Ven
2004-04-23  3:32 ` George Anzinger
2004-04-22 12:14 Martin Schwidefsky
2004-04-22 12:25 ` Arjan van de Ven
2004-04-22 11:09 Martin Schwidefsky
2004-04-22 11:14 ` Arjan van de Ven
2004-04-22 10:53 Martin Schwidefsky
2004-04-22 10:56 ` Arjan van de Ven
2004-04-22  8:55 Martin Schwidefsky
2004-04-22  8:48 Martin Schwidefsky
2004-04-22  8:52 ` Arjan van de Ven
     [not found] <1Nt5d-84u-3@gated-at.bofh.it>
     [not found] ` <1NwPD-2RW-37@gated-at.bofh.it>
     [not found]   ` <1NwPE-2RW-39@gated-at.bofh.it>
     [not found]     ` <1Nx8Y-3ev-15@gated-at.bofh.it>
2004-04-21 22:38       ` Andi Kleen
2004-04-21 16:37 Martin Schwidefsky
2004-04-21 20:43 ` Dipankar Sarma
2004-04-21 20:46   ` Christoph Hellwig
2004-04-21 21:01     ` Dipankar Sarma
2004-04-21 16:31 Martin Schwidefsky
2004-04-21 16:32 ` Christoph Hellwig
2004-04-21 14:49 Martin Schwidefsky
2004-04-21 15:31 ` Christoph Hellwig
2004-04-22  8:02 ` Arjan van de Ven

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=20040421215823.GB5014@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.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

Powered by JetHome