All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 630] [DPDK 21.02] hotplug_mp/attach_detach_virtio_user: The host display is abnormal after dpdk-hotplug_mp exits
Date: Sun, 31 Jan 2021 09:07:46 +0000	[thread overview]
Message-ID: <bug-630-3@http.bugs.dpdk.org/> (raw)

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

            Bug ID: 630
           Summary: [DPDK 21.02] hotplug_mp/attach_detach_virtio_user: The
                    host display is abnormal after dpdk-hotplug_mp exits
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: vhost/virtio
          Assignee: dev@dpdk.org
          Reporter: junx.w.zhou@intel.com
  Target Milestone: ---

Environment

DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
 21.02.0-rc2: 3021257a8111d204dc7741bd67a2502efffb6842

Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Fedora release 33 (Thirty Three)(5.9.10-200.fc33.x86_64)
Compiler: gcc (GCC) 10.2.1 20201016 (Red Hat 10.2.1-6)
Hardware platform: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz
NIC hardware: FVL_eagle(Ethernet Controller X710 for 10GbE SFP+ 1572)
NIC firmware: 
driver: i40e
version: 2.14.13
firmware-version: 8.00 0x80008b82 1.2766.0

Test Setup
Steps to reproduce
List the steps to reproduce the issue.

1.compile hotplug_mp
meson configure -Dexamples=multi_process/hotplug_mp x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

2.bind port on vfio-pci
usertools/dpdk-devbind.py --force --bind=i40e 0000:84:00.0 0000:84:00.1

3.launch testpmd
x86_64-native-linuxapp-gcc/app/dpdk-testpmd  -l 1,2 -n 4  
--file-prefix=vhost_9552_20210131070840 --no-pci --vdev
eth_vhost0,iface=/home/vhost-net -- -i

4.launch dpdk-hotplug_mp in another session
x86_64-native-linuxapp-gcc/examples/dpdk-hotplug_mp   --proc-type=auto

5.execute cmd in dpdk-hotplug_mp
1)attach
net_virtio_user0,mac=00:01:02:03:04:05,path=/home/vhost-net,packed_vq=1,mrg_rxbuf=1,in_order=0
2)detach net_virtio_user0

Show the output from the previous commands.

dpdk-hotplug_mp exits but the host display is abnormal

Expected Result
Explain what is the expected result in text or as an example output:

dpdk-hotplug_mp not exits or dpdk-hotplug_mp exits and the host display is
normal
Regression

Is this issue a regression: (Y)

Version the regression was introduced: 

commit 949735312f5ecb11110e4eec2ece1a20fef99295
Author: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tue Jan 26 11:16:35 2021 +0100

net/virtio: move vhost-user specifics to its backend

This patch moves all the Vhost-user backend specific
logic like Vhost FD, listen FD and interrupt handling
to the vhost-user backend implementation.

In order to achieve that, new ops are created to update
the link status, disconnect and reconnect the server,
and fetch the link state interrupt FD.

Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>

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

                 reply	other threads:[~2021-01-31  9:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-630-3@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 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.