From: Zhu Lingshan <lingshan.zhu@amd.com>
To: <mst@redhat.com>, <cohuck@redhat.com>, <jasowang@redhat.com>
Cc: <virtio-comment@lists.linux.dev>, <Ray.Huang@amd.com>,
Zhu Lingshan <lingshan.zhu@amd.com>
Subject: [PATCH v3 1/3] virtio: re-order device status bits
Date: Mon, 23 Jun 2025 16:36:35 +0800 [thread overview]
Message-ID: <20250623083637.296041-2-lingshan.zhu@amd.com> (raw)
In-Reply-To: <20250623083637.296041-1-lingshan.zhu@amd.com>
This commit re-orders the device status bits.
Signed-off-by: Zhu Lingshan <lingshan.zhu@amd.com>
---
content.tex | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/content.tex b/content.tex
index d3fc6a4..1efc2a5 100644
--- a/content.tex
+++ b/content.tex
@@ -36,19 +36,19 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
this bit. For example, under Linux, drivers can be loadable modules.
\end{note}
-\item[FAILED (128)] Indicates that something went wrong in the guest,
- and it has given up on the device. This could be an internal
- error, or the driver didn't like the device for some reason, or
- even a fatal error during device operation.
+\item[DRIVER_OK (4)] Indicates that the driver is set up and ready to
+ drive the device.
\item[FEATURES_OK (8)] Indicates that the driver has acknowledged all the
features it understands, and feature negotiation is complete.
-\item[DRIVER_OK (4)] Indicates that the driver is set up and ready to
- drive the device.
-
\item[DEVICE_NEEDS_RESET (64)] Indicates that the device has experienced
an error from which it can't recover.
+
+\item[FAILED (128)] Indicates that something went wrong in the guest,
+ and it has given up on the device. This could be an internal
+ error, or the driver didn't like the device for some reason, or
+ even a fatal error during device operation.
\end{description}
The \field{device status} field starts out as 0, and is reinitialized to 0 by
--
2.49.0
next prev parent reply other threads:[~2025-06-23 8:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 8:36 [PATCH v3 0/3] Implement virtio SUSPEND and RESUME feature Zhu Lingshan
2025-06-23 8:36 ` Zhu Lingshan [this message]
2025-06-26 11:39 ` [PATCH v3 1/3] virtio: re-order device status bits Parav Pandit
2025-06-23 8:36 ` [PATCH v3 2/3] virtio: document feature bit 42 Zhu Lingshan
2025-06-26 11:45 ` Parav Pandit
2025-06-26 13:06 ` Zhu, Lingshan
2025-06-23 8:36 ` [PATCH v3 3/3] virtio: introduce SUSPEND and RESUME feature Zhu Lingshan
2025-06-26 11:59 ` Parav Pandit
2025-06-26 13:25 ` Zhu, Lingshan
2025-06-26 13:40 ` Parav Pandit
2025-06-27 1:57 ` Zhu, Lingshan
2025-06-26 15:42 ` Cornelia Huck
2025-06-26 16:01 ` Parav Pandit
2025-06-27 1:46 ` Zhu, Lingshan
2025-06-27 8:27 ` Cornelia Huck
2025-06-27 11:47 ` Michael S. Tsirkin
2025-06-27 4:33 ` Parav Pandit
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=20250623083637.296041-2-lingshan.zhu@amd.com \
--to=lingshan.zhu@amd.com \
--cc=Ray.Huang@amd.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.linux.dev \
/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