From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nx4BX-0000c2-Bi for qemu-devel@nongnu.org; Wed, 31 Mar 2010 16:06:43 -0400 Received: from [140.186.70.92] (port=42349 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nx4BV-0000Zu-MA for qemu-devel@nongnu.org; Wed, 31 Mar 2010 16:06:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1Nx4BR-0006HK-Hc for qemu-devel@nongnu.org; Wed, 31 Mar 2010 16:06:41 -0400 Received: from mx20.gnu.org ([199.232.41.8]:33769) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1Nx4BR-0006HF-G8 for qemu-devel@nongnu.org; Wed, 31 Mar 2010 16:06:37 -0400 Received: from mail.codesourcery.com ([38.113.113.100]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nx4BR-0003PY-1K for qemu-devel@nongnu.org; Wed, 31 Mar 2010 16:06:37 -0400 Date: Wed, 31 Mar 2010 13:06:34 -0700 From: Nathan Froyd Subject: Re: [Qemu-devel] Re: [PATCH] vhost: fix features ack Message-ID: <20100331200634.GS18574@codesourcery.com> References: <20100331182031.GA5200@redhat.com> <4BB393CF.1040700@codemonkey.ws> <20100331153805.03ee142e@redhat.com> <20100331190753.GA6914@redhat.com> <4BB3A183.8000905@codemonkey.ws> <20100331192553.GB3274@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100331192553.GB3274@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org, Luiz Capitulino On Wed, Mar 31, 2010 at 10:25:53PM +0300, Michael S. Tsirkin wrote: > On Wed, Mar 31, 2010 at 02:24:51PM -0500, Anthony Liguori wrote: > > Long term, I think most of us want to see a single qemu executable > > that works for all architectures and compiling once is an important > > step in that direction. > > I'm not so sure. It's pretty low on my list of priorities. Most users only need > one target, speed of execution and/or features is likely much more important for them, > and these refactorings make code more generic and harder to extend.s Depends on the user, I suppose. Having 32-bit and 64-bit variants of the same architecture in a single binary would be useful. Having big-endian and little-endian variants of an architecture supported in a single binary would be useful (bonus points if you don't duplicate target-specific code excessively). Having a gigantic all-singing, all-dancing QEMU is perhaps not so useful, but between there and where we are now, there are definitely useful points. -Nathan