From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UznQY-0005dP-6M for qemu-devel@nongnu.org; Thu, 18 Jul 2013 08:35:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UznQW-0003lM-AY for qemu-devel@nongnu.org; Thu, 18 Jul 2013 08:35:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:19422) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UznQW-0003lG-24 for qemu-devel@nongnu.org; Thu, 18 Jul 2013 08:35:20 -0400 Message-ID: <51E7E0F4.5050006@redhat.com> Date: Thu, 18 Jul 2013 14:35:00 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1373624555-4403-1-git-send-email-fabio.fantoni@m2r.biz> <51DFE351.4000102@eu.citrix.com> <51E7E039.70606@suse.de> In-Reply-To: <51E7E039.70606@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com, Stefano.Stabellini@eu.citrix.com, George Dunlap , Ian.Jackson@eu.citrix.com, wei.lui2@citrix.com, qemu-devel@nongnu.org, Fabio Fantoni , Anthony Liguori Il 18/07/2013 14:31, Andreas F=E4rber ha scritto: >> > I'm just curious, why is this so complicated? Is this likely to be >> > fragile and break in the future? > As pointed out previously, the bus=3Dpci.0 bit will break with differen= t > PCI host bridges, such as the q35 machine existing today (-M q35 uses > pcie.0 instead and it has been discussed to make q35 the default at som= e > point). I had thus suggested to use a variable for the bus name to > abstract it. For -M pc-i440fx-1.5 etc. pci.0 should continue to work. I think if we ever made a PCIe machine the default, it would be different from what today's q35. In particular it probably should include a default DMI-to-PCI bridge, so as to make the command line compatible with i440FX-based machines. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH v3] libxl: usb2 and usb3 controller support for upstream qemu Date: Thu, 18 Jul 2013 14:35:00 +0200 Message-ID: <51E7E0F4.5050006@redhat.com> References: <1373624555-4403-1-git-send-email-fabio.fantoni@m2r.biz> <51DFE351.4000102@eu.citrix.com> <51E7E039.70606@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <51E7E039.70606@suse.de> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: xen-devel@lists.xensource.com, Ian.Campbell@citrix.com, Stefano.Stabellini@eu.citrix.com, George Dunlap , Ian.Jackson@eu.citrix.com, wei.lui2@citrix.com, qemu-devel@nongnu.org, Fabio Fantoni , Anthony Liguori List-Id: xen-devel@lists.xenproject.org Il 18/07/2013 14:31, Andreas F=E4rber ha scritto: >> > I'm just curious, why is this so complicated? Is this likely to be >> > fragile and break in the future? > As pointed out previously, the bus=3Dpci.0 bit will break with differen= t > PCI host bridges, such as the q35 machine existing today (-M q35 uses > pcie.0 instead and it has been discussed to make q35 the default at som= e > point). I had thus suggested to use a variable for the bus name to > abstract it. For -M pc-i440fx-1.5 etc. pci.0 should continue to work. I think if we ever made a PCIe machine the default, it would be different from what today's q35. In particular it probably should include a default DMI-to-PCI bridge, so as to make the command line compatible with i440FX-based machines. Paolo