From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Timo Suoranta <timo.suoranta@acrodea.co.jp>
Subject: Re: [Qemu-devel] ARM multithreading status
Date: Mon, 6 Jul 2009 16:31:33 +0100 [thread overview]
Message-ID: <200907061634.39206.paul@codesourcery.com> (raw)
In-Reply-To: <3646AB84-79BE-4327-A732-57661E3C8919@acrodea.co.jp>
> 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 assume you're talking about userspace emulation. For system emulation qemu
doesn't know or care how the guest handles threads, it works just like a real
machine.
Either way it sounds like a kernel bug. One process should never be able to
interfere with the rest of the system like this.
Paul
next prev parent reply other threads:[~2009-07-06 15:34 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 [this message]
2009-07-09 21:40 ` Felipe Contreras
2009-07-10 7:34 ` Timo Suoranta
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=200907061634.39206.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=timo.suoranta@acrodea.co.jp \
/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).