linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: gshan <Gavin.Shan@alcatel-lucent.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: spin_lock_irqsave and multi-core
Date: Thu, 01 Apr 2010 13:39:05 +1100	[thread overview]
Message-ID: <1270089545.7101.84.camel@pasglop> (raw)
In-Reply-To: <4BB3FE05.6040800@alcatel-lucent.com>

On Thu, 2010-04-01 at 09:59 +0800, gshan wrote:
> On multi-core system, spin_lock_irqsave() can stop all CPU cores 
> receiving interrupts?

No.

> If the answer is no, what we can do to disable external interrupt for 
> all CPU cores?

You don't :-)

Really, you generally don't. Why would you want to do that ?

Cheers,
Ben.

  reply	other threads:[~2010-04-01  2:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01  1:59 spin_lock_irqsave and multi-core gshan
2010-04-01  2:39 ` Benjamin Herrenschmidt [this message]
2010-04-01  2:41   ` gshan
2010-04-01  2:56     ` Benjamin Herrenschmidt
2010-04-01  3:18       ` gshan
2010-04-01  4:45         ` Benjamin Herrenschmidt

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=1270089545.7101.84.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=Gavin.Shan@alcatel-lucent.com \
    --cc=linuxppc-dev@lists.ozlabs.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 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).