From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1I1FFl-0004TI-Q6
	for qemu-devel@nongnu.org; Thu, 21 Jun 2007 01:30:45 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1I1FFh-0004Ss-LT
	for qemu-devel@nongnu.org; Thu, 21 Jun 2007 01:30:45 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1I1FFh-0004Sp-Fe
	for qemu-devel@nongnu.org; Thu, 21 Jun 2007 01:30:41 -0400
Received: from pentafluge.infradead.org ([213.146.154.40])
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from
	<SRS0+2a831fe47fc9d2cd0bde+1397+infradead.org+dwmw2@pentafluge.srs.infradead.org>)
	id 1I1FFh-0008Nw-54
	for qemu-devel@nongnu.org; Thu, 21 Jun 2007 01:30:41 -0400
Subject: Re: [Qemu-devel] [PATCH] Fix TLS support on x86
From: David Woodhouse <dwmw2@infradead.org>
In-Reply-To: <467958F6.2070804@suse.de>
References: <46696500.5020406@suse.de> <20070618192139.GK19155@networkno.de>
	<467958F6.2070804@suse.de>
Content-Type: text/plain
Date: Thu, 21 Jun 2007 13:31:07 +0800
Message-Id: <1182403868.2782.16.camel@shinybook.infradead.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: jakub@redhat.com

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