| To: | "linux-mips@linux-mips.org" <linux-mips@linux-mips.org> |
|---|---|
| Subject: | MIPS raw_local_irq_restore flags |
| From: | Mikael Starvik <mikael.starvik@axis.com> |
| Date: | Thu, 11 Mar 2010 15:59:44 +0100 |
| Accept-language: | sv-SE |
| Acceptlanguage: | sv-SE |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Sender: | linux-mips-bounce@linux-mips.org |
| Thread-index: | AcrBK3wkk2FBNl+9TaOxNHDqJxz80A== |
| Thread-topic: | MIPS raw_local_irq_restore flags |
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)? Best Regards /Mikael |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] MIPS: Initialize an atomic_t properly with ATOMIC_INIT(0)., Ralf Baechle |
|---|---|
| Next by Date: | some question about memory usage in mips, loody |
| Previous by Thread: | Re: [PATCH] MIPS: Initialize an atomic_t properly with ATOMIC_INIT(0)., Ralf Baechle |
| Next by Thread: | Re: MIPS raw_local_irq_restore flags, David Daney |
| Indexes: | [Date] [Thread] [Top] [All Lists] |