All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Mikael Starvik <mikael.starvik@axis.com>
Cc: "linux-mips@linux-mips.org" <linux-mips@linux-mips.org>
Subject: Re: MIPS raw_local_irq_restore flags
Date: Thu, 11 Mar 2010 09:25:43 -0800	[thread overview]
Message-ID: <4B992797.4070006@caviumnetworks.com> (raw)
In-Reply-To: <4BEA3FF3CAA35E408EA55C7BE2E61D0546AC862322@xmail3.se.axis.com>

On 03/11/2010 06:59 AM, Mikael Starvik wrote:
> For the common case CONFIG_CPU_MIPSR2&&  CONFIG_IRQ_CPU raw_local_irq_restore_flags is defined as:
>
> "       beqz    \\flags, 1f                                     \n"
> "       di                                                      \n"
> "       ei                                                      \n"
> "1:                                                             \n"
>
> Doesn't this imply that you can't do recursive local_irq_save() (with different locks ofcourse)?
>

No.  In fact local_irq_save() is intentionally designed to be used 
'recursively'.

David Daney

  reply	other threads:[~2010-03-11 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11 14:59 MIPS raw_local_irq_restore flags Mikael Starvik
2010-03-11 17:25 ` David Daney [this message]
2010-03-17  5:27 ` Ramgopal Kota
2010-03-17  6:04   ` HIGHMEM not working Ramgopal Kota
     [not found]     ` <1864acd31003170006q602602a9j5675964b886b0a55@mail.gmail.com>
     [not found]       ` <6C370B347C3FE8438C9692873287D2E1109DDF015B@SJEXCHCCR01.corp.ad.broadcom.com>
2010-03-17 11:29         ` Adam Jiang
2010-03-17 12:06           ` Ramgopal Kota
2010-03-17 16:57             ` Adam Jiang
2010-03-17 13:03   ` MIPS raw_local_irq_restore flags Ralf Baechle

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=4B992797.4070006@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mikael.starvik@axis.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 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.