From: "Michael S. Tsirkin" <mst@redhat.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] virtio: Use pci_enable_msix_exact() instead of pci_enable_msix()
Date: Sat, 22 Feb 2014 23:18:24 +0200 [thread overview]
Message-ID: <20140222211824.GA9777@redhat.com> (raw)
In-Reply-To: <20140221170128.GK17353@dhcp-26-207.brq.redhat.com>
On Fri, Feb 21, 2014 at 06:01:28PM +0100, Alexander Gordeev wrote:
> As result of deprecation of MSI-X/MSI enablement functions
> pci_enable_msix() and pci_enable_msi_block() all drivers
> using these two interfaces need to be updated to use the
> new pci_enable_msi_range() or pci_enable_msi_exact()
> and pci_enable_msix_range() or pci_enable_msix_exact()
> interfaces.
Acked-by: Michael S. Tsirkin <mst@redhat.com>
> Signed-off-by: Alexander Gordeev <agordeev@redhat.com>
> Cc: Rusty Russell <rusty@rustcorp.com.au>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: virtio-dev@lists.oasis-open.org
> Cc: virtualization@lists.linux-foundation.org
> Cc: linux-pci@vger.kernel.org
> ---
> drivers/virtio/virtio_pci.c | 6 ++----
> 1 files changed, 2 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c
> index a416f9b..101db3f 100644
> --- a/drivers/virtio/virtio_pci.c
> +++ b/drivers/virtio/virtio_pci.c
> @@ -333,10 +333,8 @@ static int vp_request_msix_vectors(struct virtio_device *vdev, int nvectors,
> for (i = 0; i < nvectors; ++i)
> vp_dev->msix_entries[i].entry = i;
>
> - /* pci_enable_msix returns positive if we can't get this many. */
> - err = pci_enable_msix(vp_dev->pci_dev, vp_dev->msix_entries, nvectors);
> - if (err > 0)
> - err = -ENOSPC;
> + err = pci_enable_msix_exact(vp_dev->pci_dev,
> + vp_dev->msix_entries, nvectors);
> if (err)
> goto error;
> vp_dev->msix_enabled = 1;
> --
> 1.7.7.6
>
> --
> Regards,
> Alexander Gordeev
> agordeev@redhat.com
next prev parent reply other threads:[~2014-02-22 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:15 [PATCH] virtio: Use pci_enable_msix_range() instead of pci_enable_msix() Alexander Gordeev
2014-02-20 1:44 ` Rusty Russell
2014-02-21 16:59 ` Alexander Gordeev
2014-02-21 17:01 ` [PATCH v2] virtio: Use pci_enable_msix_exact() " Alexander Gordeev
2014-02-22 21:18 ` Michael S. Tsirkin [this message]
2014-02-24 1:43 ` Rusty Russell
2014-02-20 5:17 ` [PATCH] virtio: Use pci_enable_msix_range() " 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=20140222211824.GA9777@redhat.com \
--to=mst@redhat.com \
--cc=agordeev@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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).