From: "Longpeng(Mike)" <longpeng2@huawei.com>
To: <jasowang@redhat.com>, <mst@redhat.com>, <sgarzare@redhat.com>,
<stefanha@redhat.com>
Cc: <virtualization@lists.linux-foundation.org>,
<kvm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<netdev@vger.kernel.org>, <arei.gonglei@huawei.com>,
<yechuan@huawei.com>, <huangzhichao@huawei.com>,
Longpeng <longpeng2@huawei.com>
Subject: [RFC 0/3] vdpa: add two ioctl commands to support generic vDPA
Date: Mon, 17 Jan 2022 17:29:18 +0800 [thread overview]
Message-ID: <20220117092921.1573-1-longpeng2@huawei.com> (raw)
From: Longpeng <longpeng2@huawei.com>
To support generic vdpa deivce[1], we need add the following ioctls:
- GET_CONFIG_SIZE: the size of the virtio config space (Patch 1)
- GET_VQS_COUNT: the count of virtqueues that exposed (Patch 2)
Patch 3 supports ctrl vq for vdpasim_net, then guys can test the
generic vDPA device on the vdpasim_net/blk.
[1] https://lore.kernel.org/all/20220105005900.860-1-longpeng2@huawei.com/
Longpeng (3):
vdpa: support exposing the config size to userspace
vdpa: support exposing the count of vqs to userspace
vdpasim_net: control virtqueue support
drivers/vdpa/vdpa_sim/vdpa_sim_net.c | 83 +++++++++++++++++++++++++++-
drivers/vhost/vdpa.c | 30 ++++++++++
include/uapi/linux/vhost.h | 7 +++
3 files changed, 118 insertions(+), 2 deletions(-)
--
2.23.0
next reply other threads:[~2022-01-17 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 9:29 Longpeng(Mike) [this message]
2022-01-17 9:29 ` [RFC 1/3] vdpa: support exposing the config size to userspace Longpeng(Mike)
2022-01-18 3:06 ` Jason Wang
2022-01-17 9:29 ` [RFC 2/3] vdpa: support exposing the count of vqs " Longpeng(Mike)
2022-01-18 3:07 ` Jason Wang
2022-03-10 3:16 ` Longpeng (Mike, Cloud Infrastructure Service Product Dept.)
2022-01-17 9:29 ` [RFC 3/3] vdpasim_net: control virtqueue support Longpeng(Mike)
2022-01-18 3:09 ` 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=20220117092921.1573-1-longpeng2@huawei.com \
--to=longpeng2@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=huangzhichao@huawei.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=yechuan@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).