From: David Woodhouse <dwmw2@infradead.org>
To: qemu-devel@nongnu.org
Cc: jakub@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Fix TLS support on x86
Date: Thu, 21 Jun 2007 13:31:07 +0800 [thread overview]
Message-ID: <1182403868.2782.16.camel@shinybook.infradead.org> (raw)
In-Reply-To: <467958F6.2070804@suse.de>
On Wed, 2007-06-20 at 18:42 +0200, Alexander Graf wrote:
> implements futexes (this is mostly done by David Woodhouse as well,
> FUTEX_WAKE_OP done by me)
#ifdef BSWAP_NEEDED, only FUTEX_OP_CMP_EQ and FUTEX_OP_CMP_NE will work
as expected. If we want to do the rest then we'll need to implement
FUTEX_OP_CMP_LT_WRONGENDIAN &c in the kernel.
Or maybe, since we don't do set_robust_list (and would need wrong-endian
support in the kernel for that too), we can assume that it's all
in-process, and hence all _within_ qemu, and we could actually implement
the futex stuff entirely within qemu with qemu's own locking?
For now I think the safer option is just to leave FUTEX_WAKE_OP
unimplemented. Jakub, what do you think?
--
dwmw2
next prev parent reply other threads:[~2007-06-21 5:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 14:17 [Qemu-devel] [PATCH] Fix TLS support on x86 Alexander Graf
2007-06-18 19:21 ` Thiemo Seufer
2007-06-20 16:42 ` Alexander Graf
2007-06-21 5:31 ` David Woodhouse [this message]
2007-06-21 6:01 ` Jakub Jelinek
2007-06-21 7:11 ` Alexander Graf
[not found] ` <20070621225550.GB25967@networkno.de>
[not found] ` <1801E7EE-FF0A-4A43-88ED-4503DEBBC831@suse.de>
[not found] ` <20070621231612.GC25967@networkno.de>
2007-07-02 10:01 ` Alexander Graf
2007-11-13 18:44 ` Stefan Weil
2007-11-13 18:46 ` Thayne Harbaugh
2007-11-13 22:13 ` Fabrice Bellard
2007-11-14 20:02 ` Stefan Weil
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=1182403868.2782.16.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=jakub@redhat.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).