From: saeed.bishara@gmail.com (saeed bishara)
To: linux-arm-kernel@lists.infradead.org
Subject: Problems with semaphores, mutexes, and atomic?
Date: Mon, 20 Jun 2011 10:20:36 +0300 [thread overview]
Message-ID: <BANLkTimDcPWOwEMxdZdPyJdYx7KLGZn2wg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikwGgrK0FFiee1a8PvDicJa-bUedg@mail.gmail.com>
On Mon, Jun 20, 2011 at 9:39 AM, Dave Hylands <dhylands@gmail.com> wrote:
> Hi,
>
> I wrote a small test module to test semaphores, mutexes and atomic
> increments, and I've tested it with CONFIG_SMP=y with 1 and 2
> processors and with CONFIG_SMP disabled.
>
> My test code can be found here:
> http://svn.hylands.org/linux/test-mutex/test-mutex.c
> (it's about 133 lines long).
yout code is not complete, the DEFINE_SEMAPHORE and DEFINE_SEMAPHORE
definitions are missing
saeed
>
next prev parent reply other threads:[~2011-06-20 7:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 6:39 Problems with semaphores, mutexes, and atomic? Dave Hylands
2011-06-20 7:20 ` saeed bishara [this message]
2011-06-20 7:44 ` Dave Hylands
2011-06-20 8:03 ` Arnd Bergmann
2011-06-20 8:21 ` Dave Hylands
2011-06-20 8:34 ` Arnd Bergmann
2011-06-20 9:07 ` Dave Hylands
2011-06-20 8:27 ` Russell King - ARM Linux
2011-06-20 8:58 ` Dave Hylands
2013-07-16 7:11 ` Hesham Mahmoud
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=BANLkTimDcPWOwEMxdZdPyJdYx7KLGZn2wg@mail.gmail.com \
--to=saeed.bishara@gmail.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 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).