From: Matej Genci <matej.genci@nutanix.com>
To: "virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Matej Genci <matej.genci@nutanix.com>
Subject: [PATCH v2] virtio: add VIRTIO_RING_NO_LEGACY
Date: Tue, 10 Sep 2019 17:53:44 +0000 [thread overview]
Message-ID: <20190910175335.231660-1-matej.genci@nutanix.com> (raw)
Add macro to disable legacy functions vring_init and vring_size.
Signed-off-by: Matej Genci <matej.genci@nutanix.com>
---
V2: Put all legacy APIs inside guards.
---
include/uapi/linux/virtio_ring.h | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/include/uapi/linux/virtio_ring.h b/include/uapi/linux/virtio_ring.h
index 4c4e24c291a5..efe5a421b4ea 100644
--- a/include/uapi/linux/virtio_ring.h
+++ b/include/uapi/linux/virtio_ring.h
@@ -118,6 +118,8 @@ struct vring_used {
struct vring_used_elem ring[];
};
+#ifndef VIRTIO_RING_NO_LEGACY
+
struct vring {
unsigned int num;
@@ -128,6 +130,8 @@ struct vring {
struct vring_used *used;
};
+#endif /* VIRTIO_RING_NO_LEGACY */
+
/* Alignment requirements for vring elements.
* When using pre-virtio 1.0 layout, these fall out naturally.
*/
@@ -135,6 +139,8 @@ struct vring {
#define VRING_USED_ALIGN_SIZE 4
#define VRING_DESC_ALIGN_SIZE 16
+#ifndef VIRTIO_RING_NO_LEGACY
+
/* The standard layout for the ring is a continuous chunk of memory which looks
* like this. We assume num is a power of 2.
*
@@ -195,6 +201,8 @@ static inline int vring_need_event(__u16 event_idx, __u16 new_idx, __u16 old)
return (__u16)(new_idx - event_idx - 1) < (__u16)(new_idx - old);
}
+#endif /* VIRTIO_RING_NO_LEGACY */
+
struct vring_packed_desc_event {
/* Descriptor Ring Change Event Offset/Wrap Counter. */
__le16 off_wrap;
--
2.22.0
next reply other threads:[~2019-09-10 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 17:53 Matej Genci [this message]
2019-09-11 9:29 ` Michael S. Tsirkin
2019-09-11 9:31 ` Michael S. Tsirkin
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=20190910175335.231660-1-matej.genci@nutanix.com \
--to=matej.genci@nutanix.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®