All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timo Suoranta <timo.suoranta@acrodea.co.jp>
To: Qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] ARM multithreading status
Date: Fri, 10 Jul 2009 10:34:51 +0300	[thread overview]
Message-ID: <4A56EF1B.8010803@acrodea.co.jp> (raw)
In-Reply-To: <94a0d4530907091440i65d16776vc1b575f9c5a8d454@mail.gmail.com>

Felipe Contreras wrote:
>> My problem is that my threading test code manages to create and join one
>> pthread, but the next pthread_create, while it starts a new thread, doesn't
>> return, and in fact the whole linux system is unable to start any new
>> processes until the test program ends.
> 
> I don't know if this helps, but I had a problem when joining a thread
> in arm linux user, and this patch fixed it:
> http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=c2764719914ff0c4d6c06adafea17629600f21ba

I'm using qemu-system-arm - so I guess the patch would not help.

I've simplified my test program - I could perhaps share a binary (or 
maybe even sources after some further cleanup) - in case someone could 
investigate this further. I've built it from the very same sources 
running 2.6.26-1 kernel on both x86 and qemu / arm.

Running on x86 Lenny in VMWare works.
Running on ARM (some real device) works.
Running on ARM Lenny in QEMU hangs.
Running on Android emulator works.

The android emulator is based on Qemu, but it uses different kernel.

I suspect there is something in the combination of QEMU and the kernel 
I'm using which makes multi threading go bad :/

--
timo

  reply	other threads:[~2009-07-10  7:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 15:16 [Qemu-devel] ARM multithreading status Timo Suoranta
2009-07-06 15:28 ` Daniel Jacobowitz
2009-07-06 15:31 ` Paul Brook
2009-07-09 21:40 ` Felipe Contreras
2009-07-10  7:34   ` Timo Suoranta [this message]
2009-07-14  8:22     ` Timo Suoranta
2009-07-14 13:03       ` Timo Suoranta
2009-07-15 20:41       ` Jamie Lokier

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=4A56EF1B.8010803@acrodea.co.jp \
    --to=timo.suoranta@acrodea.co.jp \
    --cc=qemu-devel@nongnu.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.