From: Amos Kong <akong@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: alex.williamson@redhat.com, juli@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] virtio-pci: report an error when disable msix
Date: Thu, 22 May 2014 19:40:09 +0800 [thread overview]
Message-ID: <20140522114009.GA26118@amosk.info> (raw)
In-Reply-To: <20140522091147.GB30631@redhat.com>
CC: Alex
On Thu, May 22, 2014 at 12:11:47PM +0300, Michael S. Tsirkin wrote:
> On Thu, May 22, 2014 at 05:02:17PM +0800, Amos Kong wrote:
> > QEMU remains 4k memory for PCI BAR, each msix entry takes 16 bytes.
> > If user assigns more than 128 vectors, msix resource isn't enough,
> > so msix will be disabled.
> >
> > This patch addes a note when fail to init exclusive bars for msix.
> >
> > qemu -device virtio-net-pci,netdev=h1,vectors=129,mq=on \
> > -netdev tap,id=h1,queues=8
> >
> > Signed-off-by: Amos Kong <akong@redhat.com>
>
> OK I guess, but how about removing the limit instead?
The limit of nentries had been 2048, it was changed to 128 by commit 53f94925.
If we remove this limit checking, it also can't pass sanity test,
ranges_overlap() fails.
/* Sanity test: table & pba don't overlap, fit within BARs, min aligned */
if ((table_bar_nr == pba_bar_nr &&
ranges_overlap(table_offset, table_size, pba_offset, pba_size)) ||
... ) {
return -EINVAL;
}
Related commits:
==============================================================
|commit 53f949254ad2435bfd45cb0dee96f246a0bdd7e3
|Author: Alex Williamson <alex.williamson@redhat.com>
|Date: Thu Jun 14 12:15:51 2012 -0600
|
| msix: Add simple BAR allocation MSIX setup functions
|
|diff --git a/hw/msix.c b/hw/msix.c
|index b64f109..bafea94 100644
|--- a/hw/msix.c
|+++ b/hw/msix.c
|@@ -299,6 +299,45 @@ err_config:
|@@ -299,6 +299,45 @@ err_config:
| return ret;
| }
|
|+int msix_init_exclusive_bar(PCIDevice *dev, unsigned short nentries,
|+ uint8_t bar_nr)
|+{
|+ int ret;
|+ char *name;
|+
|+ /*
|+ * Migration compatibility dictates that this remains a 4k
|+ * BAR with the vector table in the lower half and PBA in
|+ * the upper half. Do not use these elsewhere!
|+ */
^^^^^^^^^^^^^^^^^^^^^ the limit comes from here
|+#define MSIX_EXCLUSIVE_BAR_SIZE 4096
|+#define MSIX_EXCLUSIVE_BAR_PBA_OFFSET (MSIX_EXCLUSIVE_BAR_SIZE / 2)
|+
|+ if (nentries * PCI_MSIX_ENTRY_SIZE >
|MSIX_EXCLUSIVE_BAR_PBA_OFFSET) {
|+ return -EINVAL;
|+ }
> > ---
> > hw/virtio/virtio-pci.c | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/hw/virtio/virtio-pci.c b/hw/virtio/virtio-pci.c
> > index ce97514..ea5dcdf 100644
> > --- a/hw/virtio/virtio-pci.c
> > +++ b/hw/virtio/virtio-pci.c
> > @@ -976,6 +976,8 @@ static void virtio_pci_device_plugged(DeviceState *d)
> >
> > if (proxy->nvectors &&
> > msix_init_exclusive_bar(&proxy->pci_dev, proxy->nvectors, 1)) {
> > + error_report("%s: unable to init exclusive bars for msix, disable msix",
> > + __func__);
> > proxy->nvectors = 0;
> > }
> >
> > --
> > 1.9.0
--
Amos.
next prev parent reply other threads:[~2014-05-22 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 9:02 [Qemu-devel] [PATCH] virtio-pci: report an error when disable msix Amos Kong
2014-05-22 9:11 ` Michael S. Tsirkin
2014-05-22 11:40 ` Amos Kong [this message]
2014-05-22 9:20 ` Peter Maydell
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=20140522114009.GA26118@amosk.info \
--to=akong@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=juli@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).