DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: dev@dpdk.org
Cc: Tiwei Bie <tiwei.bie@intel.com>,
	Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] Deadlock when start virtio_user + vhost_kernel
Date: Wed, 12 Sep 2018 11:47:20 +0800	[thread overview]
Message-ID: <00d05c3f-ae58-7731-5473-8c1657e53100@redhat.com> (raw)

Hi:

Try to launch virtio_user + vhost_kernel with: testpmd 
--vdev=virtio_user0,path=/dev/vhost-net -- -i

It seems we get a deadlock on 
rte_rwlock_read_lock(&mcfg->memory_hotplug_lock)

calltrace:

Thread 1 "testpmd" received signal SIGINT, Interrupt.
rte_memseg_contig_walk (func=func@entry=0x555555a5e630 
<add_memory_region>, arg=arg@entry=0x7fffffffcec0)
     at /home/devel/git/dpdk/lib/librte_eal/common/eal_common_memory.c:469
469 rte_rwlock_read_lock(&mcfg->memory_hotplug_lock);
(gdb) bt
#0  rte_memseg_contig_walk (func=func@entry=0x555555a5e630 
<add_memory_region>, arg=arg@entry=0x7fffffffcec0)
     at /home/devel/git/dpdk/lib/librte_eal/common/eal_common_memory.c:469
#1  0x0000555555a5e9b1 in prepare_vhost_memory_kernel () at 
/home/devel/git/dpdk/drivers/net/virtio/virtio_user/vhost_kernel.c:118
#2  vhost_kernel_ioctl (dev=0x7ffbf5fb3300, req=<optimized out>, 
arg=<optimized out>)
     at 
/home/devel/git/dpdk/drivers/net/virtio/virtio_user/vhost_kernel.c:190
#3  0x0000555555a5f211 in virtio_user_mem_event_cb (type=<optimized 
out>, addr=<optimized out>, len=<optimized out>, arg=0x7ffbf5fb3300)
     at 
/home/devel/git/dpdk/drivers/net/virtio/virtio_user/virtio_user_dev.c:297
#4  0x000055555574814b in eal_memalloc_mem_event_notify 
(event=event@entry=RTE_MEM_EVENT_ALLOC, start=start@entry=0x7ffbf6000000,
     len=len@entry=94371840) at 
/home/devel/git/dpdk/lib/librte_eal/common/eal_common_memalloc.c:248
#5  0x00005555557563f6 in try_expand_heap_primary (contig=false, 
bound=0, align=64, flags=0, socket=0, elt_size=0, pg_sz=<optimized out>,
     heap=0x7ffff7ff667c) at 
/home/devel/git/dpdk/lib/librte_eal/common/malloc_heap.c:344
#6  try_expand_heap (heap=heap@entry=0x7ffff7ff667c, pg_sz=<optimized 
out>, elt_size=elt_size@entry=92403968, socket=socket@entry=0,
     flags=flags@entry=0, align=align@entry=64, bound=0, contig=false) 
at /home/devel/git/dpdk/lib/librte_eal/common/malloc_heap.c:426
#7  0x0000555555756928 in alloc_more_mem_on_socket 
(heap=heap@entry=0x7ffff7ff667c, size=size@entry=92403968, 
socket=socket@entry=0,
     flags=flags@entry=0, align=align@entry=64, bound=bound@entry=0, 
contig=false) at 
/home/devel/git/dpdk/lib/librte_eal/common/malloc_heap.c:554
#8  0x0000555555756e37 in heap_alloc_on_socket (contig=false, bound=0, 
align=64, flags=0, socket=0, size=92403968, type=<optimized out>)
     at /home/devel/git/dpdk/lib/librte_eal/common/malloc_heap.c:590
#9  malloc_heap_alloc (type=<optimized out>, size=92403968, 
socket_arg=<optimized out>, flags=0, align=<optimized out>, bound=0, 
contig=false)
     at /home/devel/git/dpdk/lib/librte_eal/common/malloc_heap.c:626
#10 0x0000555555753fc1 in rte_zmalloc () at 
/home/devel/git/dpdk/lib/librte_eal/common/rte_malloc.c:74
#11 0x00005555556192f9 in init_port () at 
/home/devel/git/dpdk/app/test-pmd/testpmd.c:2645
#12 main (argc=4, argv=0x7fffffffdb18) at 
/home/devel/git/dpdk/app/test-pmd/testpmd.c:2734

And I also get this warning:

vhost_kernel_ioctl(): VHOST_SET_OWNER failed: Device or resource busy

Both looks like a bug that needs to be fixed.

Thanks

             reply	other threads:[~2018-09-12  3:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  3:47 Jason Wang [this message]
2018-09-12  4:27 ` Tiwei Bie
2018-09-12  8:14   ` Jason Wang

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=00d05c3f-ae58-7731-5473-8c1657e53100@redhat.com \
    --to=jasowang@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=tiwei.bie@intel.com \
    /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).