From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: when spin_lock_irq (as opposed to spin_lock_irqsave) is appropriate?
Date: Sat, 11 Oct 2008 19:29:01 +0400 [thread overview]
Message-ID: <200810111929.01927.arvidjaar@mail.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Logically, one piece of kernel code has no way to know whether another
piece of kernel code (or may be hard-/firmware) has disabled some
interrupt line. So it looks like spin_lock_irq should not even exist,
except may be for very specific cases (where we are sure no other piece
of kernel code may run concurrently)?
Sorry for stupid question, I an not actually a HW type of person ...
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-10-11 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-11 15:29 Andrey Borzenkov [this message]
2008-10-11 15:41 ` when spin_lock_irq (as opposed to spin_lock_irqsave) is appropriate? Oliver Neukum
2008-10-11 15:55 ` Andrey Borzenkov
2008-10-12 8:08 ` Oliver Neukum
2008-10-11 16:18 ` Arjan van de Ven
2008-10-12 11:48 ` Andrey Borzenkov
2008-10-12 22:21 ` Arnd Bergmann
2008-10-12 23:12 ` 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=200810111929.01927.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=linux-kernel@vger.kernel.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