From: Liuxiangdong <liuxiangdong5@huawei.com>
To: <xieyongji@bytedance.com>
Cc: "Fangyi (Eric)" <eric.fangyi@huawei.com>,
<yebiaoxiang@huawei.com>, <x86@kernel.org>, <kvm@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v13 00/13] Introduce VDUSE - vDPA Device in Userspace
Date: Mon, 11 Oct 2021 15:32:49 +0800 [thread overview]
Message-ID: <6163E8A1.8080901@huawei.com> (raw)
In-Reply-To: <20210831103634.33-1-xieyongji@bytedance.com>
Hi, Yongji.
I tried vduse with null-blk:
$ qemu-storage-daemon \
--chardev socket,id=charmonitor,path=/tmp/qmp.sock,server,nowait \
--monitor chardev=charmonitor \
--blockdev
driver=host_device,cache.direct=on,aio=native,filename=/dev/nullb0,node-name=disk0
\
--export
type=vduse-blk,id=test,node-name=disk0,writable=on,name=vduse-null,num-queues=16,queue-size=128
The qemu-storage-daemon is yours
(https://github.com/bytedance/qemu/tree/vduse)
And then, how can we use this vduse-null (dev/vduse/vduse-null) in vm(QEMU)?
Because qemu-storage-daemon open this vduse-null in vduse_dev_init(),
all the operations which open this dev
will report "failed to open '/dev/vduse/vduse-null': Device or resource
busy".
Or something I understood wrong?
Thanks!
Xiangdong Liu
next prev parent reply other threads:[~2021-10-11 7:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 10:36 [PATCH v13 00/13] Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-08-31 10:36 ` [PATCH v13 01/13] iova: Export alloc_iova_fast() and free_iova_fast() Xie Yongji
2021-08-31 10:36 ` [PATCH v13 02/13] eventfd: Export eventfd_wake_count to modules Xie Yongji
2021-09-01 2:50 ` Jason Wang
2021-08-31 10:36 ` [PATCH v13 03/13] file: Export receive_fd() " Xie Yongji
2021-09-05 15:57 ` Michael S. Tsirkin
2021-09-05 16:44 ` Al Viro
2021-08-31 10:36 ` [PATCH v13 04/13] vdpa: Fix some coding style issues Xie Yongji
2021-08-31 10:36 ` [PATCH v13 05/13] vdpa: Add reset callback in vdpa_config_ops Xie Yongji
2021-09-06 5:55 ` Michael S. Tsirkin
2021-09-06 6:09 ` Yongji Xie
2021-09-06 6:37 ` Michael S. Tsirkin
2021-09-06 7:06 ` Yongji Xie
2021-09-06 8:00 ` Michael S. Tsirkin
2021-09-06 8:45 ` Yongji Xie
2021-09-06 10:43 ` Michael S. Tsirkin
2021-09-06 12:13 ` Yongji Xie
2021-08-31 10:36 ` [PATCH v13 06/13] vhost-vdpa: Handle the failure of vdpa_reset() Xie Yongji
2021-08-31 10:36 ` [PATCH v13 07/13] vhost-iotlb: Add an opaque pointer for vhost IOTLB Xie Yongji
2021-08-31 10:36 ` [PATCH v13 08/13] vdpa: Add an opaque pointer for vdpa_config_ops.dma_map() Xie Yongji
2021-08-31 10:36 ` [PATCH v13 09/13] vdpa: factor out vhost_vdpa_pa_map() and vhost_vdpa_pa_unmap() Xie Yongji
2021-08-31 10:36 ` [PATCH v13 10/13] vdpa: Support transferring virtual addressing during DMA mapping Xie Yongji
2021-08-31 10:36 ` [PATCH v13 11/13] vduse: Implement an MMU-based software IOTLB Xie Yongji
2021-08-31 10:36 ` [PATCH v13 12/13] vduse: Introduce VDUSE - vDPA Device in Userspace Xie Yongji
2021-08-31 10:36 ` [PATCH v13 13/13] Documentation: Add documentation for VDUSE Xie Yongji
2021-10-11 7:32 ` Liuxiangdong [this message]
2021-10-11 8:31 ` [PATCH v13 00/13] Introduce VDUSE - vDPA Device in Userspace Yongji Xie
2021-10-11 8:32 ` Yongji Xie
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=6163E8A1.8080901@huawei.com \
--to=liuxiangdong5@huawei.com \
--cc=eric.fangyi@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
--cc=xieyongji@bytedance.com \
--cc=yebiaoxiang@huawei.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).