All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Wei W" <wei.w.wang@intel.com>
To: Daniel Verkamp <dverkamp@chromium.org>,
	"virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>
Cc: Cornelia Huck <cohuck@redhat.com>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: RE: [PATCH v2 2/2] virtio-pci: check name when counting MSI-X vectors
Date: Sun, 5 Jan 2020 12:27:19 +0000	[thread overview]
Message-ID: <286AC319A985734F985F78AFA26841F73E39206A__38101.5021748439$1578227255$gmane$org@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20200103184044.73568-2-dverkamp@chromium.org>

On Saturday, January 4, 2020 2:41 AM, Daniel Verkamp wrote:
> Subject: [PATCH v2 2/2] virtio-pci: check name when counting MSI-X vectors
> 
> VQs without a name specified are not valid; they are skipped in the later loop
> that assigns MSI-X vectors to queues, but the per_vq_vectors loop above that
> counts the required number of vectors previously still counted any queue with a
> non-NULL callback as needing a vector.
> 
> Add a check to the per_vq_vectors loop so that vectors with no name are not
> counted to make the two loops consistent.  This prevents over-counting
> unnecessary vectors (e.g. for features which were not negotiated with the
> device).
> 
> Cc: stable@vger.kernel.org
> Fixes: 86a559787e6f ("virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT")
> Reviewed-by: Cornelia Huck <cohuck@redhat.com>
> Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
> ---
> 
> v1:
> https://lists.linuxfoundation.org/pipermail/virtualization/2019-December/0448
> 28.html
> 
>  drivers/virtio/virtio_pci_common.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/virtio/virtio_pci_common.c
> b/drivers/virtio/virtio_pci_common.c
> index f2862f66c2ac..222d630c41fc 100644
> --- a/drivers/virtio/virtio_pci_common.c
> +++ b/drivers/virtio/virtio_pci_common.c
> @@ -294,7 +294,7 @@ static int vp_find_vqs_msix(struct virtio_device *vdev,
> unsigned nvqs,
>  		/* Best option: one for change interrupt, one per vq. */
>  		nvectors = 1;
>  		for (i = 0; i < nvqs; ++i)
> -			if (callbacks[i])
> +			if (names[i] && callbacks[i])
>  				++nvectors;
>  	} else {
>  		/* Second best: one for change, shared for all vqs. */
> --
> 2.24.1.735.g03f4e72817-goog

Reviewed-by: Wang, Wei W <wei.w.wang@intel.com>

Best,
Wei

  reply	other threads:[~2020-01-05 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-03 18:40 [PATCH v2 1/2] virtio-balloon: initialize all vq callbacks Daniel Verkamp
2020-01-03 18:40 ` [PATCH v2 2/2] virtio-pci: check name when counting MSI-X vectors Daniel Verkamp
2020-01-05 12:27   ` Wang, Wei W [this message]
2020-01-05 12:27   ` Wang, Wei W
2020-01-03 18:40 ` Daniel Verkamp
2020-01-05 12:24 ` [PATCH v2 1/2] virtio-balloon: initialize all vq callbacks Wang, Wei W
2020-01-05 13:25   ` Michael S. Tsirkin
2020-01-05 13:25   ` Michael S. Tsirkin
2020-01-05 12:24 ` Wang, Wei W

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='286AC319A985734F985F78AFA26841F73E39206A__38101.5021748439$1578227255$gmane$org@shsmsx102.ccr.corp.intel.com' \
    --to=wei.w.wang@intel.com \
    --cc=cohuck@redhat.com \
    --cc=dverkamp@chromium.org \
    --cc=mst@redhat.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.