From: Alex Williamson <alex.williamson@redhat.com>
To: qemu-devel@nongnu.org
Cc: avi@redhat.com, kvm@vger.kernel.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] pci: Add generic PCI device option to disable 64bit MMIO BARs
Date: Wed, 01 Feb 2012 16:44:07 -0700 [thread overview]
Message-ID: <1328139847.6937.272.camel@bling.home> (raw)
In-Reply-To: <20120201225203.26724.82424.stgit@bling.home>
On Wed, 2012-02-01 at 15:57 -0700, Alex Williamson wrote:
> As we start to enable 64bit I/O devices, there's a good chance
> we'll find bugs and compatibility issues. This allows a user
> to toggle off (default on) 64bit PCI MMIO BARs, downgrading
> them to 32bit BARs.
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
>
> Should this be an "x-mem64" option implying that it's really
> only for debugging and may go away or could this have some
> longevity?
>
> hw/pci.c | 18 ++++++++++++++++++
> hw/pci.h | 4 ++++
> 2 files changed, 22 insertions(+), 0 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index 57ec104..9afddb0 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -63,6 +63,8 @@ struct BusInfo pci_bus_info = {
> QEMU_PCI_CAP_MULTIFUNCTION_BITNR, false),
> DEFINE_PROP_BIT("command_serr_enable", PCIDevice, cap_present,
> QEMU_PCI_CAP_SERR_BITNR, true),
> + DEFINE_PROP_BIT("mem64", PCIDevice, cap_present,
> + QEMU_PCI_CAP_MEM64_BITNR, true),
> DEFINE_PROP_END_OF_LIST()
> }
> };
> @@ -957,6 +959,22 @@ void pci_register_bar(PCIDevice *pci_dev, int region_num,
> exit(1);
> }
>
> + if (!(type & PCI_BASE_ADDRESS_SPACE_IO)) {
> + if (!(pci_dev->cap_present & QEMU_PCI_CAP_MEM64)) {
> + type &= ~PCI_BASE_ADDRESS_MEM_TYPE_64;
> + }
> +
> + /* 32bit BARs are limited to 2GB */
> + if (size >= 0x80000000U && !(type & PCI_BASE_ADDRESS_MEM_TYPE_64)) {
Oops, this should just be >, not >=. I'll wait to see if this has any
legs before respinning.
> + fprintf(stderr, "Device %04x:%02x:%02x.%x BAR %d is %ld "
> + "GB, 64bit memory type required\n",
> + pci_find_domain(pci_dev->bus), pci_bus_num(pci_dev->bus),
> + PCI_SLOT(pci_dev->devfn), PCI_FUNC(pci_dev->devfn),
> + region_num, (long)(size >> 30));
> + exit(1);
> + }
> + }
> +
> r = &pci_dev->io_regions[region_num];
> r->addr = PCI_BAR_UNMAPPED;
> r->size = size;
> diff --git a/hw/pci.h b/hw/pci.h
> index 4220151..17fd996 100644
> --- a/hw/pci.h
> +++ b/hw/pci.h
> @@ -126,6 +126,10 @@ enum {
> /* command register SERR bit enabled */
> #define QEMU_PCI_CAP_SERR_BITNR 4
> QEMU_PCI_CAP_SERR = (1 << QEMU_PCI_CAP_SERR_BITNR),
> +
> + /* expose 64bit MMIO BARs when available */
> +#define QEMU_PCI_CAP_MEM64_BITNR 5
> + QEMU_PCI_CAP_MEM64 = (1 << QEMU_PCI_CAP_MEM64_BITNR),
> };
>
> typedef int (*msix_mask_notifier_func)(PCIDevice *, unsigned vector,
>
prev parent reply other threads:[~2012-02-01 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 22:57 [Qemu-devel] [PATCH] pci: Add generic PCI device option to disable 64bit MMIO BARs Alex Williamson
2012-02-01 23:14 ` Michael S. Tsirkin
2012-02-01 23:25 ` Alex Williamson
2012-02-01 23:44 ` Alex Williamson [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=1328139847.6937.272.camel@bling.home \
--to=alex.williamson@redhat.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--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).