From: "Michael S. Tsirkin" <mst@redhat.com>
To: qemu-devel@nongnu.org
Cc: =?UTF-8?q?Herv=C3=A9=20Poussineau?= <hpoussin@reactos.org>,
"Richard Henderson" <rth@twiddle.net>
Subject: [Qemu-devel] [PULL 08/14] pci: remove explicit check to 64K ioport size
Date: Sun, 29 Sep 2013 10:00:08 +0300 [thread overview]
Message-ID: <1380437951-21788-9-git-send-email-mst@redhat.com> (raw)
In-Reply-To: <1380437951-21788-1-git-send-email-mst@redhat.com>
From: Hervé Poussineau <hpoussin@reactos.org>
This check is useless, as bigger addresses will be ignored when
added to 'io' MemoryRegion, which has a size of 64K.
However, some architectures don't use the 'io' MemoryRegion, like
the alpha and versatile platforms. They create a PCI I/O region
bigger than 64K, so let them handle PCI I/O BARs in the higher range.
MST: reinstated work-around for BAR sizing.
Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
Reviewed-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
---
hw/pci/pci.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/hw/pci/pci.c b/hw/pci/pci.c
index 52cbab7..00554a0 100644
--- a/hw/pci/pci.c
+++ b/hw/pci/pci.c
@@ -1028,8 +1028,10 @@ static pcibus_t pci_bar_address(PCIDevice *d,
}
new_addr = pci_get_long(d->config + bar) & ~(size - 1);
last_addr = new_addr + size - 1;
- /* NOTE: we have only 64K ioports on PC */
- if (last_addr <= new_addr || new_addr == 0 || last_addr > UINT16_MAX) {
+ /* Check if 32 bit BAR wraps around explicitly.
+ * TODO: make priorities correct and remove this work around.
+ */
+ if (last_addr <= new_addr || new_addr == 0 || last_addr >= UINT32_MAX) {
return PCI_BAR_UNMAPPED;
}
return new_addr;
--
MST
next prev parent reply other threads:[~2013-09-29 6:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-29 6:59 [Qemu-devel] [PULL 00/14] pc,pci,virtio fixes and cleanups Michael S. Tsirkin
2013-09-29 6:59 ` [Qemu-devel] [PULL 01/14] q35: make pci window address/size match guest cfg Michael S. Tsirkin
2013-09-29 6:59 ` [Qemu-devel] [PULL 02/14] range: add Range to typedefs Michael S. Tsirkin
2013-09-29 6:59 ` [Qemu-devel] [PULL 03/14] range: add min/max operations on ranges Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 04/14] pci: add helper to retrieve the 64-bit range Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 05/14] q35: use 64 bit window programmed by guest Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 06/14] piix: " Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 07/14] piix4: disable io on reset Michael S. Tsirkin
2013-09-29 7:00 ` Michael S. Tsirkin [this message]
2013-09-29 7:00 ` [Qemu-devel] [PULL 09/14] virtio-net: fix up HMP NIC info string " Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 10/14] smbios: Normalize smbios_entry_add()'s error handling to exit(1) Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 11/14] smbios: Convert to QemuOpts Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 12/14] smbios: Improve diagnostics for conflicting entries Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 13/14] smbios: Make multiple -smbios type= accumulate sanely Michael S. Tsirkin
2013-09-29 7:00 ` [Qemu-devel] [PULL 14/14] smbios: Factor out smbios_maybe_add_str() Michael S. Tsirkin
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=1380437951-21788-9-git-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=hpoussin@reactos.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).