From: rcrewe@plxtech.com (Richard Crewe)
To: linux-arm-kernel@lists.infradead.org
Subject: LDREX/STREX and pre-emption on SMP hardware
Date: Fri, 21 Aug 2009 16:07:34 +0100 [thread overview]
Message-ID: <4A8EB836.3000406@plxtech.com> (raw)
Section A2.9.3 of the ARM architecture ref. manual seems to imply that
ldrex/strex instruction pairs won't work correctly if they are nested
due to pre-emption.
Should a strex instruction be added to the low-level interrupt handler
or should all ldrex/strex instruction pairs be protected from
pre-emption by disabling interrupts?
I have a suspicion that this may only cause problems on SMP systems.
--
Rich
next reply other threads:[~2009-08-21 15:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 15:07 Richard Crewe [this message]
2009-08-21 15:42 ` LDREX/STREX and pre-emption on SMP hardware Catalin Marinas
2009-08-21 15:50 ` Jamie Lokier
2009-08-21 15:58 ` Catalin Marinas
2009-08-21 21:29 ` David Xiao
2009-08-24 15:44 ` Catalin Marinas
2009-08-24 17:14 ` David Xiao
2009-08-24 17:41 ` Catalin Marinas
2009-08-24 18:59 ` David Xiao
2009-09-14 1:43 ` Jamie Lokier
2009-09-14 8:53 ` Catalin Marinas
2009-09-14 10:00 ` Russell King - ARM Linux
2009-09-14 10:06 ` Catalin Marinas
2009-09-14 11:47 ` Catalin Marinas
2009-09-14 12:21 ` Catalin Marinas
2009-09-14 12:43 ` Bill Gatliff
2009-09-14 12:57 ` Catalin Marinas
2009-09-14 19:30 ` Bill Gatliff
2009-09-14 14:09 ` Russell King - ARM Linux
2009-09-14 14:21 ` Russell King - ARM Linux
2009-09-14 14:26 ` Catalin Marinas
2009-09-14 15:35 ` Catalin Marinas
2009-09-14 23:16 ` Jamie Lokier
2009-09-14 14:23 ` Russell King - ARM Linux
2009-09-14 14:29 ` Catalin Marinas
2009-09-18 20:20 ` Russell King - ARM Linux
2009-09-18 22:51 ` Catalin Marinas
2009-08-24 21:12 ` Jamie Lokier
2009-08-25 8:33 ` Catalin Marinas
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=4A8EB836.3000406@plxtech.com \
--to=rcrewe@plxtech.com \
--cc=linux-arm-kernel@lists.infradead.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.