From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NA2i7-0005gs-3M for qemu-devel@nongnu.org; Mon, 16 Nov 2009 09:37:43 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NA2i2-0005g4-Io for qemu-devel@nongnu.org; Mon, 16 Nov 2009 09:37:42 -0500 Received: from [199.232.76.173] (port=40069 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NA2i2-0005g1-Do for qemu-devel@nongnu.org; Mon, 16 Nov 2009 09:37:38 -0500 Received: from mx20.gnu.org ([199.232.41.8]:50895) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NA2i2-0006w1-5P for qemu-devel@nongnu.org; Mon, 16 Nov 2009 09:37:38 -0500 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NA2hz-0001D6-Ul for qemu-devel@nongnu.org; Mon, 16 Nov 2009 09:37:36 -0500 From: Paul Brook Subject: Re: [Qemu-devel] Re: [PATCH 01/12] TCG "sync" op Date: Mon, 16 Nov 2009 14:37:32 +0000 References: <1256133153-3121-1-git-send-email-uli@suse.de> <200911110056.48147.paul@codesourcery.com> <4B015986.6040704@suse.de> In-Reply-To: <4B015986.6040704@suse.de> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200911161437.32519.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: riku.voipio@iki.fi, qemu-devel@nongnu.org, Aurelien Jarno > > While sync appears attractive as a quick hack to achieve this, I think it > > is liable to be abused, and cause us serious pain long-term. If you need > > an easy solution then use ld/st (as with ARM VFP registers). If you want > > a good solution then fix whichever bit of TCG makes accessing a pair of > > registers horribly slow. We already have some support for this > > (concat_i32_i64). > > Could we please include it nevertheless? I don't want to see S390 TCG > and KVM targets not included because of this sync operation. > > If you like, add some big fat warning around it and maybe break > compilation if anyone but the s390 target uses that sync op, but let's > not keep a whole target from inclusion because of a single feature that > _might_ one day affect others. I'd rather not include sync, and instead use the explicit ld/st code you already wrote. Paul