Isn't the problem that both CONFIG_IBMVIO and CONFIG_PCI are defined?
I had to see what IBMVIO was, it looks like the IBM Virtual I/O Server. Although you actually fixed the bug, the other bug might be that IBMVIO is defined when it's "The VIOS is part of the PowerVM® Editions hardware feature"
QEMU (with its pseries machine type) doesn't actually run the PowerVM hypervisor, but rather it directly implements a very similar hypervisor-guest interface (based on the Power Architecture Platform Reference and Open Firmware) such that they are treated as the same hardware platform in Linux's eyes.
QEMU is also capable of emulating a variety of other PowerPC machine types, including PowerNV/OpenPOWER bare-metal systems, various Power Macs, RS/6000s etc.
Comments
Isn't the problem that both CONFIG_IBMVIO and CONFIG_PCI are defined?
I had to see what IBMVIO was, it looks like the IBM Virtual I/O Server. Although you actually fixed the bug, the other bug might be that IBMVIO is defined when it's "The VIOS is part of the PowerVM® Editions hardware feature"
Were you on an IBM power box?
https://www.ibm.com/docs/en/power8?topic=server-virtual-io-o...
I'm just curious, because the IFDEFs assume one-or-the-other as written. Is having both busses a valid configuration?
Author here, having both buses is a valid configuration and completely expected for running Linux under the PowerVM hypervisor.
That's interesting, I didn't know QEMU could emulate PPC well enough to run that.
Thanks!
QEMU (with its pseries machine type) doesn't actually run the PowerVM hypervisor, but rather it directly implements a very similar hypervisor-guest interface (based on the Power Architecture Platform Reference and Open Firmware) such that they are treated as the same hardware platform in Linux's eyes.
QEMU is also capable of emulating a variety of other PowerPC machine types, including PowerNV/OpenPOWER bare-metal systems, various Power Macs, RS/6000s etc.