From: dan@debian.org (Daniel Jacobowitz)
To: linux-arm-kernel@lists.infradead.org
Subject: Problems with pthread on ARM/PXA270
Date: Wed, 16 Sep 2009 10:40:51 -0400 [thread overview]
Message-ID: <20090916144051.GA19307@caradoc.them.org> (raw)
In-Reply-To: <200909160926.02036.schindele@nentec.de>
On Wed, Sep 16, 2009 at 09:26:01AM +0200, Juergen Schindele wrote:
> Hello all,
> we tried to implement a thread based software on our PXA270 based platform but
> we had trouble with pthreads. So i modyfied a tiny progam to test. This little progam creates
> 10 threads and each thread does print something (an index an a pointer to itself).
>
> On my PC with Suse 11.0 Linux (kernel 2.6.27) this works fine as supposed to.
> Each thread has his turn and print his own values.
>
> But on our pxa270 platform the thread switch does not (or really rarely) happen
> and only one thread is printing always the same values. So i suppose thread
> switching is not working!
>
> Any hints or experiences are welcome !!!
It's just a wild guess, but check your sched_clock implementation. I
fixed a similar problem in QEMU last week; the kernel used to function
OK with sched_clock always returning zero, but some time between
2.6.25 and 2.6.28 became dependent on it.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-09-16 14:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 7:26 Problems with pthread on ARM/PXA270 Juergen Schindele
2009-09-16 14:14 ` Eric Miao
2009-09-16 15:01 ` Juergen Schindele
2009-09-16 15:06 ` Eric Miao
2009-09-17 7:35 ` Juergen Schindele
2009-09-17 12:47 ` Beckwith, Stephen (Stephen)
2009-09-17 13:06 ` Juergen Schindele
2009-09-21 21:19 ` Beckwith, Stephen (Stephen)
2009-09-16 14:40 ` Daniel Jacobowitz [this message]
2009-09-18 10:06 ` Juergen Schindele
2009-09-18 14:10 ` Daniel Jacobowitz
2009-09-16 22:01 ` Jamie Lokier
2009-09-16 22:54 ` [arm-gnu] " James
2009-09-18 7:53 ` Uwe Kleine-König
2009-09-18 12:48 ` Jamie Lokier
2009-09-24 8:34 ` Juergen Schindele
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=20090916144051.GA19307@caradoc.them.org \
--to=dan@debian.org \
--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).