From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug in ARM thumb usermode emulation
Date: Mon, 18 Sep 2006 21:56:48 +0100 [thread overview]
Message-ID: <200609182156.49174.paul@codesourcery.com> (raw)
In-Reply-To: <564d96fb0609181343m45ff7a76p5a110ef5c896b30a@mail.gmail.com>
> What must be done for implementing TLS + multithread in qemu? Maybe I can
> help.
* Implement the TLS syscalls (futexes and the architecture specific bits).
There's a patch for clone() here: https://nowt.dyndns.org/patch.qemu_nptl
* Fix all the bits of qemu that aren't threadsafe (mainly the TB cache IIRC).
* Fix guest atomic operations, and make sure guest coherency/ordering
guaranteed are honoured, even which not guaranteed natively by the host.
Note that this only applies to usermode emulation. Full system emulation works
fine because this is all handled by the guest kernel, exactly the same as on
real hardware.
Paul
next prev parent reply other threads:[~2006-09-18 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 20:05 [Qemu-devel] bug in ARM thumb usermode emulation Rafael Espíndola
2006-09-18 20:16 ` Paul Brook
2006-09-18 20:43 ` Rafael Espíndola
2006-09-18 20:56 ` Paul Brook [this message]
2006-09-19 20:36 ` Rafael Espíndola
2006-09-29 10:59 ` Rafael Espíndola
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=200609182156.49174.paul@codesourcery.com \
--to=paul@codesourcery.com \
--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 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).