From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:39433) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNzW1-0006zp-ND for qemu-devel@nongnu.org; Wed, 18 Feb 2015 02:57:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YNzVx-0005FI-MU for qemu-devel@nongnu.org; Wed, 18 Feb 2015 02:57:49 -0500 Received: from mail-wg0-x232.google.com ([2a00:1450:400c:c00::232]:58464) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YNzVx-0005FA-G7 for qemu-devel@nongnu.org; Wed, 18 Feb 2015 02:57:45 -0500 Received: by mail-wg0-f50.google.com with SMTP id l2so40588307wgh.9 for ; Tue, 17 Feb 2015 23:57:44 -0800 (PST) Sender: Paolo Bonzini Message-ID: <54E445F3.3070802@redhat.com> Date: Wed, 18 Feb 2015 08:57:39 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1424235596-29024-1-git-send-email-david@gibson.dropbear.id.au> In-Reply-To: <1424235596-29024-1-git-send-email-david@gibson.dropbear.id.au> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Make i82801b11 and ioh3420 x86 only by default List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: David Gibson , mst@redhat.com, yamahata@valinux.co.jp Cc: qemu-devel@nongnu.org On 18/02/2015 05:59, David Gibson wrote: > As PCI devices, the i82801b11 and ioh3420 devices could theoretically exist > on any platform with a PCI bus. However in practice, they're Intel > specific devices, They can be used as a generic PCIe root port and PCIe-to-PCI bridge, they're not Intel-specific as long as your firmware doesn't care about the vendor and device id. > that are very unlikely to appear on anything other than > an x86. Therefore this patch gives them their own config options, enabled > only for x86 targets by default. I think it's quite likely that we'll use them, or at least ioh3420, on any PCIe machine. So you probably want to add ioh3420 to arm-softmmu and aarch64-softmmu as well. I don't know about i82801b11, but it doesn't hurt to have it in ARM/AArch64 either. Also, the same can be done for xio3130, so you can also limit that one to x86 and ARM/Aarch64. Paolo