DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1161] [dpdk-23.03]virtio_user_as_exceptional_path/vhost_exception_path_with_virtio_user: launch testpmd as virtio-user failed
Date: Mon, 20 Feb 2023 01:50:09 +0000	[thread overview]
Message-ID: <bug-1161-3-69IGt0MSsP@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-1161-3@http.bugs.dpdk.org/>

[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1161

lingwei (weix.ling@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|IN_PROGRESS                 |RESOLVED
         Resolution|---                         |FIXED

--- Comment #3 from lingwei (weix.ling@intel.com) ---
Patch have merged into the DPDK main branch.

Verified PASSED.

OS: Ubuntu 22.04.1 LTS/Linux 5.15.45-051545-generic

NIC hardware: Intel Ethernet Controller XL710 for 40GbE QSFP+ 1583

Driver/NIC firmware: i40e-2.22.8/firmware-version: 9.10 0x8000d01e 1.3295.0

commit be26e898ffb3a1719c88bf025d45a847d3a60ffc
Author: Maxime Coquelin <maxime.coquelin@redhat.com>
Date:   Fri Feb 17 13:31:19 2023 +0100

    net/virtio-user: fix vhost-kernel initialization

    This patch fixes a regression causing devices with
    Vhost-kernel backends initialization to fail.

    Indeed, Vhost-kernel backend init expects
    dev->max_queue_pairs to be set at setup time, while its
    assignment was moved after backend setup when adding
    control queue support for Vhost-vdpa backends.

    It is safe to set dev->max_queue_pairs early for
    Vhost-kernel backends as if the backend does not support
    multiqueue, its setup will fail.

    Bugzilla ID: 1161
    Fixes: 7be724856315 ("net/virtio-user: get max number of queue pairs from
device")

    Reported-by: Wei Ling <weix.ling@intel.com>
    Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 4054 bytes --]

      reply	other threads:[~2023-02-20  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  3:12 bugzilla
2023-02-20  1:50 ` bugzilla [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=bug-1161-3-69IGt0MSsP@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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).