All of lore.kernel.org
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Andy Whitcroft <apw@shadowen.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	hari@in.ibm.com, Andrew Morton <akpm@osdl.org>,
	rddunlap@osdl.org, linux-kernel@vger.kernel.org,
	jamesclv@us.ibm.com
Subject: Re: BUG_ON(!cpus_equal(cpumask, tmp));
Date: Thu, 1 Apr 2004 10:34:13 +0530	[thread overview]
Message-ID: <20040401050413.GA4056@in.ibm.com> (raw)
In-Reply-To: <109577502.1080783067@[192.168.0.89]>

On Thu, Apr 01, 2004 at 01:31:15AM +0000, Andy Whitcroft wrote:
> 	spin_lock(&tlbstate_lock);
> +
> +	/* Subtle, mask the request mask with the currently online cpu's.
> +	 * Sample this under the lock; cpus in the the middle of going
> +	 * offline will wait until there is noone in this critical section
> +	 * before disabling IPI handling. */
> +	cpus_and(tmp, cpumask, cpu_online_map);
> +	if(cpus_empty(tmp))
> +		return;

Hmm ..Doesn't it need to drop tlbstate_lock before returning?

> +	/* Subtle, IPI users assume that they will be able to get IPI's
> +	 * though to the cpus listed in cpu_online_map.  To ensure this
> +	 * we add the requirement that they check cpu_online_map within
> +	 * the IPI critical sections.  Here we remove ourselves from the
> +	 * map, then ensure that all other cpus have left the relevant
> +	 * critical sections since the change.  We do this by aquiring
> +	 * the relevant section locks, if we have them none else is in
> +	 * them.  Once this is done we can go offline. */
> +	spin_lock(&tlbstate_lock);
> +	spin_unlock(&tlbstate_lock);
> +	spin_lock(&tlbstate_lock);
> +	spin_unlock(&tlbstate_lock);

The second lock should be call_lock?


-- 


Thanks and Regards,
Srivatsa Vaddagiri,
Linux Technology Center,
IBM Software Labs,
Bangalore, INDIA - 560017

  reply	other threads:[~2004-04-01  5:03 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-29 15:39 BUG_ON(!cpus_equal(cpumask, tmp)); Martin J. Bligh
2004-03-30  0:21 ` Andrew Morton
2004-03-30  0:25   ` Andrew Morton
2004-03-30 13:28     ` Hariprasad Nellitheertha
2004-03-30 23:17       ` Randy.Dunlap
2004-03-31  0:22         ` Martin J. Bligh
2004-03-31  0:39           ` Andrew Morton
2004-03-31  0:57             ` Martin J. Bligh
2004-03-31  1:11               ` Andrew Morton
2004-03-31  1:24                 ` Martin J. Bligh
2004-03-31  1:36                   ` Andrew Morton
2004-03-31  1:51                     ` Martin J. Bligh
2004-03-31  4:43                       ` Hariprasad Nellitheertha
2004-04-01  0:31                         ` Andy Whitcroft
2004-04-01  5:04                           ` Srivatsa Vaddagiri [this message]
2004-04-01 11:38                             ` Andy Whitcroft
2004-04-02 18:33                               ` Randy.Dunlap
2004-04-01  8:42                         ` Paul Jackson
2004-04-01 13:57                           ` Hariprasad Nellitheertha
2004-04-03  1:45                             ` Andy Whitcroft
2004-03-31  1:01           ` Andy Whitcroft
  -- strict thread matches above, loose matches on Subject: below --
2004-01-02 23:51 Martin J. Bligh

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=20040401050413.GA4056@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=akpm@osdl.org \
    --cc=apw@shadowen.org \
    --cc=hari@in.ibm.com \
    --cc=jamesclv@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=rddunlap@osdl.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.