qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Marcel Apfelbaum <marcel@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	mst@redhat.com, ehabkost@redhat.com
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-ppc@nongnu.org,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] pxb: Restrict to x86
Date: Fri, 6 Jan 2017 08:26:25 +0200	[thread overview]
Message-ID: <4ac9d2ba-6887-7207-b17e-d06109ccaba2@gmail.com> (raw)
In-Reply-To: <53dcb2da-fa15-63b0-5849-325b6edcac83@redhat.com>

On 01/06/2017 08:13 AM, Marcel Apfelbaum wrote:
> On 01/06/2017 07:04 AM, David Gibson wrote:
>> The PCI Expander Bridge (PXB) device is essentially a hack to allow
>> different PCIe devices to be assigned to different NUMA nodes on x86.  Each
>> PXB is sort-of a separate PCI host bridge, except that its config space
>> is shared with the config space of the main PCI host bridge, rather than
>> being independent.
>>
>
> Hi David,
>
>> This is only necessary if the platform doesn't (easily) allow truly
>> independent PCI host bridges.  AFAIK that's just x86.
>>
>
> Indeed, it is possible to support independent PCI host bridges on x86 by
> using a separate MMCONFIG space for each one and enable separate PCI domains.
> We simply didn't need this until now, but maybe will be implemented it in the future.
>
>> This patch makes it possible to configure PXB out of the build, and adjusts
>> the default configs so it's only included on x86 targets.
>>
>
> Makes sense

Actually ACPI based ARM guests may be able to use the PXB as well,
let's wait for their opinion.

Thanks,
Marcel

>
> Reviewed-by: Marcel Apfelbaum <marcel@redhat.com>
>
> Thanks,
> Marcel
>
>> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
>> ---
>>  default-configs/i386-softmmu.mak   | 1 +
>>  default-configs/x86_64-softmmu.mak | 1 +
>>  hw/pci-bridge/Makefile.objs        | 2 +-
>>  3 files changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/default-configs/i386-softmmu.mak b/default-configs/i386-softmmu.mak
>> index 0b51360..6c52d26 100644
>> --- a/default-configs/i386-softmmu.mak
>> +++ b/default-configs/i386-softmmu.mak
>> @@ -56,3 +56,4 @@ CONFIG_IOH3420=y
>>  CONFIG_I82801B11=y
>>  CONFIG_SMBIOS=y
>>  CONFIG_HYPERV_TESTDEV=$(CONFIG_KVM)
>> +CONFIG_PXB=y
>> diff --git a/default-configs/x86_64-softmmu.mak b/default-configs/x86_64-softmmu.mak
>> index 7f89503..2d0341c 100644
>> --- a/default-configs/x86_64-softmmu.mak
>> +++ b/default-configs/x86_64-softmmu.mak
>> @@ -56,3 +56,4 @@ CONFIG_IOH3420=y
>>  CONFIG_I82801B11=y
>>  CONFIG_SMBIOS=y
>>  CONFIG_HYPERV_TESTDEV=$(CONFIG_KVM)
>> +CONFIG_PXB=y
>> diff --git a/hw/pci-bridge/Makefile.objs b/hw/pci-bridge/Makefile.objs
>> index f2adfe3..5612bd7 100644
>> --- a/hw/pci-bridge/Makefile.objs
>> +++ b/hw/pci-bridge/Makefile.objs
>> @@ -1,5 +1,5 @@
>>  common-obj-y += pci_bridge_dev.o
>> -common-obj-y += pci_expander_bridge.o
>> +common-obj-$(CONFIG_PXB) += pci_expander_bridge.o
>>  common-obj-$(CONFIG_XIO3130) += xio3130_upstream.o xio3130_downstream.o
>>  common-obj-$(CONFIG_IOH3420) += ioh3420.o
>>  common-obj-$(CONFIG_I82801B11) += i82801b11.o
>>
>
>

  reply	other threads:[~2017-01-06  6:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06  5:04 [Qemu-devel] [RFC] pxb: Restrict to x86 David Gibson
2017-01-06  6:13 ` Marcel Apfelbaum
2017-01-06  6:26   ` Marcel Apfelbaum [this message]
2017-01-06 19:41   ` Michael S. Tsirkin
2017-01-08  8:17     ` Marcel Apfelbaum
2017-01-08 23:48       ` David Gibson
2017-01-09  1:58         ` Michael S. Tsirkin
2017-01-09  2:54           ` David Gibson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ac9d2ba-6887-7207-b17e-d06109ccaba2@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ehabkost@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).