Received: from eggs.gnu.org ([209.51.188.92]:53584) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hCKlf-0008LJ-GU for qemu-devel@nongnu.org; Fri, 05 Apr 2019 05:04:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hCKkW-0004Nl-L9 for qemu-devel@nongnu.org; Fri, 05 Apr 2019 05:03:01 -0400 Received: from mout.gmx.net ([212.227.17.22]:56783) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hCKkV-0004Ht-TN for qemu-devel@nongnu.org; Fri, 05 Apr 2019 05:03:00 -0400 References: <20190404185730.GA22512@ls3530.dellerweb.de> <20190405082613.GC6105@redhat.com> From: Helge Deller Message-ID: <457ec791-3691-2ebb-e225-bd42a7aee627@gmx.de> Date: Fri, 5 Apr 2019 11:02:52 +0200 MIME-Version: 1.0 In-Reply-To: <20190405082613.GC6105@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH] configure: Automatically fall back to TCI on non-release architectures List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?Q?Daniel_P=2e_Berrang=c3=a9?= Cc: Peter Maydell , =?UTF-8?Q?Philippe_Mathieu-Daud=c3=a9?= , QEMU Developers On 05.04.19 10:26, Daniel P. Berrang=C3=A9 wrote: > On Fri, Apr 05, 2019 at 09:56:46AM +0200, Helge Deller wrote: >> Hi Peter, >> >> On 05.04.19 03:34, Peter Maydell wrote: >>> On Fri, 5 Apr 2019 at 01:59, Helge Deller wrote: >>>> If a non-release architecture is found, and it's known that there is = no >>>> native TCG support for that CPU, automatically fall back to the TCI >>>> implementation instead of requesting the user to run configure again >>>> with the --enable-tcg-interpreter option. >>>> >>>> This change simplifies building qemu in automatic build environments >>>> (like in my case the debian buildds) because one does not need to >>>> special case on the architectures. >>> >>> I don't think we should do this. TCI is unmaintained, has several >>> known flaws, >> >> Just out of interest: Is there a list with those flaws somewhere? >> >>> does not provide the level of performance that >>> people expect from QEMU, and we've talked about removing it >>> altogether. In particular, distros should not automatically ship >>> a TCI QEMU -- it's something that a user can use if they >>> explicitly opt into but which I don't think we want to surprise >>> anybody with. >> >> I won't argue against your points. They are all valid. >> >>> If we care about a host architecture we should support it >>> with a proper TCG backend. If we don't care that much we >>> shouldn't support it. >> >> Looking just at some of the debian "ports" (non-release) architectures: >> alpha, hppa, ia64, m68k, powerpc, sh4, sparc64 >> Most likely nobody will ever care enough to write a TCG backend for tho= se, >> and it doesn't even make sense because they are so much slower than >> the currently supported TCG backend architectures. So why should one wa= nt >> to emulate a fast x86 machine on slow m68k for example? >> >> The only reason when it *can* make sense is, when you need "basic" >> emulation or availability of binaries for cross-dependecies in distros, >> e.g. to build other packages or to be able to install other packages. >> As one example, many packages depend on libvirt (frontend tools, monito= ring >> stuff, ...) and libvirt again depends on some qemu binaries. >> So, having qemu buildable (even if the result is slow) makes life easie= r. > > If it is just a matter of satisfying dependencies, it is easy to build > a minimal libvirt that is essentially just the client libraries and not > the QEMU driver that would in turn allow other packages to build. Altern= atively > it should be possible to build the downstream apps with their libvirt de= p > disabled avoiding pulling in the whole virtualization chain as a build > pre-req. libvirt was just one example, and yes, it's possible to work around in multiple ways. As another example, even if I only want to build "qemu-img", I still need to manually give the --enable-tcg-interpreter configure option. >> I know, my point above now turns into a "distro packaging" issue. >> That's why I'm questioning, why should distros (or even direct end-user= s) >> be forced to distinguish between architectures? >> Shouldn't running "./configure" find out what's available and then >> auto-configure itself to the *best* what's possible? > > "best" depends on the POV. You want configure to enable support on > hppa by default since you have an interest in that architecture, which > is fine. The QEMU maintainers, however, have a POV that considers > raising an error by default to be the "best" solution for architectures > that are considered unsupported, requiring explicit arg to optin to use > unsupported features. Yes, fair point. Sadly such special treatment by projects makes life for me as an architecture maintainer much harder :-( Helge