From: Launchpad Bug Tracker <1900919@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1900919] Re: PXB selected as root bus incorrectly
Date: Fri, 09 Jul 2021 04:17:25 -0000 [thread overview]
Message-ID: <162580424582.19936.3904166426976106968.malone@loganberry.canonical.com> (raw)
In-Reply-To: 160331877993.30496.14778848047318719784.malonedeb@chaenomeles.canonical.com
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1900919
Title:
PXB selected as root bus incorrectly
Status in QEMU:
Expired
Bug description:
release: 4c41341af76cfc85b5a6c0f87de4838672ab9f89
qdev_device_add() will search for the "closest" bus possible, and bail out early if that bus is a root bus. pxb devices are considered root buses and so if you either
1. Add a PCI device on the QEMU command line *after* a pxb device, or
2. Add an integrated PCI device (like a watchdog)
#1: -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52 -device ahci,id=sata0,addr=0x8
#2: -watchdog i6300esb -device pxb-pcie,id=cxl.0,bus=pcie.0,bus_nr=52
The PXB will get selected as the bus (instead of the real root bus)
and this will cause an assertion failure with the message like "qemu-
system-x86_64: -device ahci,id=sata0,addr=0x8: PCI: Only PCI/PCIe
bridges can be plugged into pxb-pcie"
I think this is relatively solvable in the code base by determining if
a bus is an expander, and skipping it if so. However, I wonder if it
makes more sense to just allow expanders to have endpoint devices.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1900919/+subscriptions
prev parent reply other threads:[~2021-07-09 4:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 22:19 [Bug 1900919] [NEW] PXB selected as root bus incorrectly bwidawsk
2021-05-09 14:33 ` [Bug 1900919] " Thomas Huth
2021-07-09 4:17 ` Launchpad Bug Tracker [this message]
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=162580424582.19936.3904166426976106968.malone@loganberry.canonical.com \
--to=1900919@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.