qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [0/2] pseries: Rework PCI code for handling multiple PHBs
@ 2012-11-27  6:07 David Gibson
  2012-11-27  6:07 ` [Qemu-devel] [PATCH 1/2] pseries: Don't allow TCE (iommu) tables to be registered with duplicate LIOBNs David Gibson
                   ` (2 more replies)
  0 siblings, 3 replies; 10+ messages in thread
From: David Gibson @ 2012-11-27  6:07 UTC (permalink / raw)
  To: agraf, mst; +Cc: qemu-ppc, qemu-devel

Hi Michael, Alex,

This patch represents a compromise I hope will be acceptable after the
long thread discussing handling of multiple PCI host bridges on the
pseries machine.  Patch 1/1 is just a preliminary enforcing uniqueness
of LIOBNs in the IOMMU code.

Patch 2/2 is the meat.  It allows either explicit configuration of all
the properties, or the user can just set an abstract index which will
generate sensible and probably-unique values for all the rest.

With these patches I was able to do something like:
	qemu-system-ppc64 -M pseries -m 1024 -nographic \
	fc17-root.qcow2 -net none -device nec-usb-xhci -device \
	spapr-pci-host-bridge,index=1 -device e1000,netdev=fred \
	-netdev user,id=fred

I was able to see both the PCI domains in the guest, and use the NIC
on the secondary domain.

There are still some gotches with multiple domains though.  The domain
value in PCIHostBus is still always initialized to 0, and there are
other places in the PCI core where handling of multiple domains is
essentially stubbed out.

Michael, any thoughts on what to do about that?  I could fix up the
PCI code so that domain is actually set and used.  But I think the
whole notion of domain numbers is kind of bogus on the qemu side:
since PCI domains are completely independent from each other, it's
only platform convention which determines what the domain numbers are.
On platforms that don't have a strong convention, the guest will
number them itself and we have no way of knowing that.  So it seems to
me that the PCI code should instead of domain numbers just use the
device ID, or the bus name or some qemu side symbolic name.  For
platforms that do have a numbering convention those names can be
derived from the domain numbers, but it also works for platforms that
don't.

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, other threads:[~2012-12-11 10:00 UTC | newest]

Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-11-27  6:07 [Qemu-devel] [0/2] pseries: Rework PCI code for handling multiple PHBs David Gibson
2012-11-27  6:07 ` [Qemu-devel] [PATCH 1/2] pseries: Don't allow TCE (iommu) tables to be registered with duplicate LIOBNs David Gibson
2012-12-10 13:00   ` Michael S. Tsirkin
2012-12-11  9:59     ` Alexander Graf
2012-11-27  6:07 ` [Qemu-devel] [PATCH 2/2] pseries: Properly handle allocation of multiple PCI host bridges David Gibson
2012-11-28  2:50   ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-12-10 13:00   ` [Qemu-devel] " Michael S. Tsirkin
2012-11-27 12:36 ` [Qemu-devel] [0/2] pseries: Rework PCI code for handling multiple PHBs Michael S. Tsirkin
2012-11-28  2:50   ` [Qemu-devel] [Qemu-ppc] " David Gibson
2012-12-10 12:58     ` Michael S. Tsirkin

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).