qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Longpeng(Mike)" via <qemu-devel@nongnu.org>
To: <stefanha@redhat.com>, <mst@redhat.com>, <cohuck@redhat.com>,
	<sgarzare@redhat.com>
Cc: <pbonzini@redhat.com>, <arei.gonglei@huawei.com>,
	<yechuan@huawei.com>, <huangzhichao@huawei.com>,
	<qemu-devel@nongnu.org>, Longpeng <longpeng2@huawei.com>
Subject: [PATCH v3 02/10] update linux headers
Date: Sat, 19 Mar 2022 15:20:04 +0800	[thread overview]
Message-ID: <20220319072012.525-3-longpeng2@huawei.com> (raw)
In-Reply-To: <20220319072012.525-1-longpeng2@huawei.com>

From: Longpeng <longpeng2@huawei.com>

Update linux headers to 5.xxx (kernel part is not merged yet)

To support generic vdpa deivce, we need add the following ioctls:
- VHOST_VDPA_GET_CONFIG_SIZE: get the configuration size.
- VHOST_VDPA_GET_VQS_COUNT: get the count of supported virtqueues.

Signed-off-by: Longpeng <longpeng2@huawei.com>
---
 linux-headers/linux/vhost.h | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/linux-headers/linux/vhost.h b/linux-headers/linux/vhost.h
index c998860d7b..5d99e7c242 100644
--- a/linux-headers/linux/vhost.h
+++ b/linux-headers/linux/vhost.h
@@ -150,4 +150,11 @@
 /* Get the valid iova range */
 #define VHOST_VDPA_GET_IOVA_RANGE	_IOR(VHOST_VIRTIO, 0x78, \
 					     struct vhost_vdpa_iova_range)
+
+/* Get the config size */
+#define VHOST_VDPA_GET_CONFIG_SIZE	_IOR(VHOST_VIRTIO, 0x79, __u32)
+
+/* Get the count of all virtqueues */
+#define VHOST_VDPA_GET_VQS_COUNT	_IOR(VHOST_VIRTIO, 0x80, __u32)
+
 #endif
-- 
2.23.0



  parent reply	other threads:[~2022-03-19  7:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19  7:20 [PATCH v3 00/10] add generic vDPA device support Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 01/10] virtio: get class_id and pci device id by the virtio id Longpeng(Mike) via
2022-03-19  7:20 ` Longpeng(Mike) via [this message]
2022-03-19  7:20 ` [PATCH v3 03/10] vdpa: add the infrastructure of vdpa-dev Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 04/10] vdpa-dev: implement the instance_init/class_init interface Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 05/10] vdpa-dev: implement the realize interface Longpeng(Mike) via
2022-03-28 14:59   ` Stefano Garzarella
2022-03-29  5:01     ` longpeng2--- via
2022-03-29  5:15     ` longpeng2--- via
2022-03-29  7:05       ` Stefano Garzarella
2022-03-19  7:20 ` [PATCH v3 06/10] vdpa-dev: implement the unrealize interface Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 07/10] vdpa-dev: implement the get_config/set_config interface Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 08/10] vdpa-dev: implement the get_features interface Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 09/10] vdpa-dev: implement the set_status interface Longpeng(Mike) via
2022-03-19  7:20 ` [PATCH v3 10/10] vdpa-dev: mark the device as unmigratable Longpeng(Mike) via
2022-03-28 15:11 ` [PATCH v3 00/10] add generic vDPA device support Stefano Garzarella
2022-03-29  5:20   ` longpeng2--- via

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=20220319072012.525-3-longpeng2@huawei.com \
    --to=qemu-devel@nongnu.org \
    --cc=arei.gonglei@huawei.com \
    --cc=cohuck@redhat.com \
    --cc=huangzhichao@huawei.com \
    --cc=longpeng2@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    --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).