From: Tiwei Bie <tiwei.bie@intel.com>
To: mst@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
jasowang@redhat.com, virtio-dev@lists.oasis-open.org
Cc: cunming.liang@intel.com
Subject: [virtio-dev] [RFC] VIRTIO_F_IO_BARRIER: use I/O barriers in driver
Date: Wed, 25 Apr 2018 16:23:12 +0800 [thread overview]
Message-ID: <20180425082312.32244-1-tiwei.bie@intel.com> (raw)
There will be hardware virtio devices in the future, which
require drivers to use the barriers suitable for I/O device,
compared with software virtio devices which just require
drivers to use the barriers suitable for CPU core.
To fix the ordering issue for hardware virtio devices, add
a new feature: VIRTIO_F_IO_BARRIER. When negotiated, driver
will use the barriers suitable for I/O device.
Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
---
content.tex | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/content.tex b/content.tex
index ae5fa4c..f24e320 100644
--- a/content.tex
+++ b/content.tex
@@ -5445,6 +5445,8 @@ Descriptors} and \ref{sec:Packed Virtqueues / Indirect Flag: Scatter-Gather Supp
that drivers pass extra data (besides identifying the Virtqueue)
in their device notifications.
See \ref{sec:Virtqueues / Driver notifications}~\nameref{sec:Virtqueues / Driver notifications}.
+ \item[VIRTIO_F_IO_BARRIER(37)] This feature indicates that the device
+ needs the driver to use the barriers suitable for hardware device.
\end{description}
\drivernormative{\section}{Reserved Feature Bits}{Reserved Feature Bits}
@@ -5460,6 +5462,10 @@ addresses to the device.
A driver SHOULD accept VIRTIO_F_RING_PACKED if it is offered.
+A driver SHOULD accept VIRTIO_F_IO_BARRIER if it is offered.
+If VIRTIO_F_IO_BARRIER has been negotiated, a driver MUST use
+the barriers suitable for hardware device.
+
\devicenormative{\section}{Reserved Feature Bits}{Reserved Feature Bits}
A device MUST offer VIRTIO_F_VERSION_1. A device MAY fail to operate further
@@ -5473,6 +5479,9 @@ accepted.
If VIRTIO_F_IN_ORDER has been negotiated, a device MUST use
buffers in the same order in which they have been available.
+A device MAY fail to operate further if VIRTIO_F_IO_BARRIER
+is not accepted.
+
\section{Legacy Interface: Reserved Feature Bits}\label{sec:Reserved Feature Bits / Legacy Interface: Reserved Feature Bits}
Transitional devices MAY offer the following:
--
2.11.0
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next reply other threads:[~2018-04-25 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 8:23 Tiwei Bie [this message]
2018-04-25 13:23 ` [virtio-dev] Re: [RFC] VIRTIO_F_IO_BARRIER: use I/O barriers in driver Paolo Bonzini
2018-04-25 13:52 ` Tiwei Bie
2018-04-25 14:29 ` Michael S. Tsirkin
2018-04-28 0:35 ` Paolo Bonzini
2018-04-27 13:02 ` Stefan Hajnoczi
2018-04-28 1:42 ` Tiwei Bie
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=20180425082312.32244-1-tiwei.bie@intel.com \
--to=tiwei.bie@intel.com \
--cc=cunming.liang@intel.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-dev@lists.oasis-open.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