From: Marcel Apfelbaum <marcel@redhat.com>
To: qemu-devel@nongnu.org
Cc: marcel@redhat.com, lersek@redhat.com, mst@redhat.com
Subject: [Qemu-devel] [PATCH] hw/pci: do not update the PCI mappings while Decode (I/O or memory) bit is not set in the Command register
Date: Mon, 11 Jan 2016 14:24:23 +0200 [thread overview]
Message-ID: <1452515063-5615-1-git-send-email-marcel@redhat.com> (raw)
Two reasons:
- PCI Spec indicates that while the bit is not set
the memory sizing is not finished.
- pci_bar_address will return PCI_BAR_UNMAPPED
and a previous value can be accidentally overridden
if the command register is modified (and not the BAR).
Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
---
Hi,
I found this when trying to use multiple root complexes with OVMF.
When trying to attach a device to the pxb-pcie device as Integrated
Device it did not receive the IO/MEM resources.
The reason is that OVMF is working like that:
1. It disables the Decode (I/O or memory) bit in the Command register
2. It configures the device BARS
3. Makes some tests on the Command register
4. ...
5. Enables the Decode (I/O or memory) at some point.
On step 3 all the BARS are overridden to 0xffffffff by QEMU.
Since QEMU uses the device BARs to compute the new host bridge resources
it now gets garbage.
Laszlo, this also solves the SHPC problem for the pci-2-pci bridge inside the pxb.
Now we can enable the SHPC for it too.
Thanks,
Marcel
hw/pci/pci.c | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index 168b9cc..f9127dc 100644
--- a/hw/pci/pci.c
+++ b/hw/pci/pci.c
@@ -1148,6 +1148,7 @@ static void pci_update_mappings(PCIDevice *d)
PCIIORegion *r;
int i;
pcibus_t new_addr;
+ uint16_t cmd = pci_get_word(d->config + PCI_COMMAND);
for(i = 0; i < PCI_NUM_REGIONS; i++) {
r = &d->io_regions[i];
@@ -1156,6 +1157,22 @@ static void pci_update_mappings(PCIDevice *d)
if (!r->size)
continue;
+ /*
+ * Do not update the mappings until the command register's
+ * Decode (I/O or memory) bit is not set. Two reasons:
+ * - PCI Spec indicates that while the bit is not set
+ * the memory sizing is not finished.
+ * - pci_bar_address will return PCI_BAR_UNMAPPED
+ * and a previous value can be accidentally overridden
+ * if the command register is modified (and not the BAR).
+ * */
+ if (((r->type & PCI_BASE_ADDRESS_SPACE_IO) &&
+ !(cmd & PCI_COMMAND_IO)) ||
+ ((r->type != PCI_BASE_ADDRESS_SPACE_IO) &&
+ !(cmd & PCI_COMMAND_MEMORY))) {
+ continue;
+ }
+
new_addr = pci_bar_address(d, i, r->type, r->size);
/* This bar isn't changed */
--
2.4.3
next reply other threads:[~2016-01-11 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-11 12:24 Marcel Apfelbaum [this message]
2016-01-11 14:07 ` [Qemu-devel] [PATCH] hw/pci: do not update the PCI mappings while Decode (I/O or memory) bit is not set in the Command register Igor Mammedov
2016-01-11 15:10 ` Marcel Apfelbaum
2016-01-11 16:11 ` Laszlo Ersek
2016-01-11 16:34 ` Marcel Apfelbaum
2016-01-11 17:15 ` Laszlo Ersek
2016-01-11 18:01 ` Marcel Apfelbaum
2016-01-11 18:44 ` Laszlo Ersek
2016-01-11 18:57 ` Marcel Apfelbaum
2016-01-14 12:24 ` Marcel Apfelbaum
2016-01-14 14:30 ` Laszlo Ersek
2016-01-14 14:49 ` Michael S. Tsirkin
2016-01-14 15:23 ` Marcel Apfelbaum
2016-01-14 15:37 ` Michael S. Tsirkin
2016-01-14 17:20 ` Marcel Apfelbaum
2016-01-14 17:28 ` Michael S. Tsirkin
2016-01-14 18:25 ` Marcel Apfelbaum
2016-01-14 15:14 ` Marcel Apfelbaum
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=1452515063-5615-1-git-send-email-marcel@redhat.com \
--to=marcel@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--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 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).