Skip to contentSkip to conversation

clarify device reset

PATCH In review Cornelia Huck 4 participants 6 messages Jan 28, 2021 – May 11, 2021

lore
Share & tools
lore
#0 lore raw

PATCH v4 1/1 clarify device reset

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

---

Stefan, Halil: I did not apply your R-b due to the amount of changes.

v3 -> v4:
- moved device status 're-initialize to 0' clause that is now duplicated to an informal description
- more clarifications on when reset may be used and device requirements
- use \field{device status} consistently
RFC v2 -> v3:
- re-worded the "must not send notifications" clause to avoid guessing
- added a driver conformance clause on how a driver should find out when reset is complete
RFC -> RFC v2:
- moved reset spec to basic facilities

---
 conformance.tex |  2 ++
 content.tex     | 24 +++++++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)
conformance.tex +2 -0
index e78adfdbd283..17c390d249db 100644
@@ -64,6 +64,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Message Framing}
@@ -283,6 +284,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Message Framing}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Descriptor Table}
content.tex +23 -1
index 1ca24c13f2d0..47239b877c6c 100644
@@ -51,6 +51,9 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
   an error from which it can't recover.
 \end{description}
 
+The \field{device status} field starts out as 0, and is reinitialized to 0 by
+the device during reset.
+
 \drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
 The driver MUST update \field{device status},
 setting bits to indicate the completed steps of the driver
@@ -71,7 +74,6 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
 \end{note}
 
 \devicenormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The device MUST initialize \field{device status} to 0 upon reset.
 
 The device MUST NOT consume buffers or send any used buffer
 notifications to the driver before DRIVER_OK.
@@ -193,6 +195,26 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 terminology. Occasionally, the term event is used to refer to
 a notification or a receipt of a notification.
 
+\section{Device Reset}\label{sec:Basic Facilities of a Virtio Device / Device Reset}
+
+The driver may want to initiate a device reset at various times; notably,
+it is required to do so during device initialization and device cleanup.
+
+The mechanism used by the driver to initiate the reset is transport specific.
+
+\devicenormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+A device MUST reinitialize \field{device status} to 0 after receiving a reset.
+
+A device MUST NOT send notifications or interact with the queues after
+indicating completion of the reset by reinitializing \field{device status}
+to 0, until the driver re-initializes the device.
+
+\drivernormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+The driver SHOULD consider a driver-initiated reset complete when it
+reads \field{device status} as 0.
+
 \section{Device Configuration Space}\label{sec:Basic Facilities of a Virtio Device / Device Configuration Space}
 
 Device configuration space is generally used for rarely-changing or
Signature · 18 lines
2.26.2


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
Reviewed-by on v4 1/1
#1 lore raw
Quoted 21 lines · Cornelia Huck

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

---

Stefan, Halil: I did not apply your R-b due to the amount of changes.

v3 -> v4:
- moved device status 're-initialize to 0' clause that is now duplicated to an informal description
- more clarifications on when reset may be used and device requirements
- use \field{device status} consistently
RFC v2 -> v3:
- re-worded the "must not send notifications" clause to avoid guessing
- added a driver conformance clause on how a driver should find out when reset is complete
RFC -> RFC v2:
- moved reset spec to basic facilities

Quoted 4 lines
---
  conformance.tex |  2 ++
  content.tex     | 24 +++++++++++++++++++++++-
  2 files changed, 25 insertions(+), 1 deletion(-)
Quoted 60 lines
conformance.tex +2 -0
index e78adfdbd283..17c390d249db 100644
@@ -64,6 +64,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
  \begin{itemize}
  \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Status Field}
  \item \ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset}
  \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Configuration Space}
  \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
  \item \ref{drivernormative:Basic Facilities of a Virtio Device / Message Framing}
@@ -283,6 +284,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
  \begin{itemize}
  \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Status Field}
  \item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset}
  \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Configuration Space}
  \item \ref{devicenormative:Basic Facilities of a Virtio Device / Message Framing}
  \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Descriptor Table}
content.tex +16 -1
index 1ca24c13f2d0..47239b877c6c 100644
@@ -51,6 +51,9 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
    an error from which it can't recover.
  \end{description}
 
+The \field{device status} field starts out as 0, and is reinitialized to 0 by
+the device during reset.
+
  \drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
  The driver MUST update \field{device status},
  setting bits to indicate the completed steps of the driver
@@ -71,7 +74,6 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
  \end{note}
 
  \devicenormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The device MUST initialize \field{device status} to 0 upon reset.
 
  The device MUST NOT consume buffers or send any used buffer
  notifications to the driver before DRIVER_OK.
@@ -193,6 +195,26 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
  terminology. Occasionally, the term event is used to refer to
  a notification or a receipt of a notification.
 
+\section{Device Reset}\label{sec:Basic Facilities of a Virtio Device / Device Reset}
+
+The driver may want to initiate a device reset at various times; notably,
+it is required to do so during device initialization and device cleanup.
+
+The mechanism used by the driver to initiate the reset is transport specific.
+
+\devicenormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+A device MUST reinitialize \field{device status} to 0 after receiving a reset.
+
+A device MUST NOT send notifications or interact with the queues after
+indicating completion of the reset by reinitializing \field{device status}

content.tex \section{Notifications}\label{sec:Basic Facilities of a Virtio Device · line 220

Quoted 10 lines
content.tex +7 -0
+to 0, until the driver re-initializes the device.
+
+\drivernormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+The driver SHOULD consider a driver-initiated reset complete when it
+reads \field{device status} as 0.
+
  \section{Device Configuration Space}\label{sec:Basic Facilities of a Virtio Device / Device Configuration Space}
 
  Device configuration space is generally used for rarely-changing or

This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/

#2 lore raw
In reply to Cornelia Huck
Quoted 3 lines · On Thu, 28 Jan 2021 14:52:35 +0100 Cornelia Huck <[email protected]> wrote:

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

Quoted 82 lines

---

Stefan, Halil: I did not apply your R-b due to the amount of changes.

v3 -> v4:
- moved device status 're-initialize to 0' clause that is now duplicated to an informal description
- more clarifications on when reset may be used and device requirements
- use \field{device status} consistently
RFC v2 -> v3:
- re-worded the "must not send notifications" clause to avoid guessing
- added a driver conformance clause on how a driver should find out when reset is complete
RFC -> RFC v2:
- moved reset spec to basic facilities

---
 conformance.tex |  2 ++
 content.tex     | 24 +++++++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)
conformance.tex +2 -0
index e78adfdbd283..17c390d249db 100644
@@ -64,6 +64,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Message Framing}
@@ -283,6 +284,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Message Framing}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Descriptor Table}
content.tex +16 -1
index 1ca24c13f2d0..47239b877c6c 100644
@@ -51,6 +51,9 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
   an error from which it can't recover.
 \end{description}
 
+The \field{device status} field starts out as 0, and is reinitialized to 0 by
+the device during reset.
+
 \drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
 The driver MUST update \field{device status},
 setting bits to indicate the completed steps of the driver
@@ -71,7 +74,6 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
 \end{note}
 
 \devicenormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The device MUST initialize \field{device status} to 0 upon reset.
 
 The device MUST NOT consume buffers or send any used buffer
 notifications to the driver before DRIVER_OK.
@@ -193,6 +195,26 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 terminology. Occasionally, the term event is used to refer to
 a notification or a receipt of a notification.
 
+\section{Device Reset}\label{sec:Basic Facilities of a Virtio Device / Device Reset}
+
+The driver may want to initiate a device reset at various times; notably,
+it is required to do so during device initialization and device cleanup.
+
+The mechanism used by the driver to initiate the reset is transport specific.
+
+\devicenormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+A device MUST reinitialize \field{device status} to 0 after receiving a reset.
+
+A device MUST NOT send notifications or interact with the queues after
+indicating completion of the reset by reinitializing \field{device status}

content.tex \section{Notifications}\label{sec:Basic Facilities of a Virtio Device · line 220

Quoted 10 lines
content.tex +7 -0
+to 0, until the driver re-initializes the device.
+
+\drivernormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+The driver SHOULD consider a driver-initiated reset complete when it
+reads \field{device status} as 0.
+
 \section{Device Configuration Space}\label{sec:Basic Facilities of a Virtio Device / Device Configuration Space}
 
 Device configuration space is generally used for rarely-changing or

This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/

Reviewed-by on v4 1/1
#3 lore raw
In reply to Cornelia Huck
Quoted 5 lines · On Thu, 28 Jan 2021 14:52:35 +0100 Cornelia Huck <[email protected]> wrote:

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/

#4 lore raw
In reply to Cornelia Huck
Quoted 61 lines · Cornelia Huck

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

---

Stefan, Halil: I did not apply your R-b due to the amount of changes.

v3 -> v4:
- moved device status 're-initialize to 0' clause that is now duplicated to an informal description
- more clarifications on when reset may be used and device requirements
- use \field{device status} consistently
RFC v2 -> v3:
- re-worded the "must not send notifications" clause to avoid guessing
- added a driver conformance clause on how a driver should find out when reset is complete
RFC -> RFC v2:
- moved reset spec to basic facilities

---
 conformance.tex |  2 ++
 content.tex     | 24 +++++++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)
conformance.tex +2 -0
index e78adfdbd283..17c390d249db 100644
@@ -64,6 +64,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Virtqueues}
 \item \ref{drivernormative:Basic Facilities of a Virtio Device / Message Framing}
@@ -283,6 +284,7 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets}
 \begin{itemize}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Status Field}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Feature Bits}
+\item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Reset}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Device Configuration Space}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Message Framing}
 \item \ref{devicenormative:Basic Facilities of a Virtio Device / Virtqueues / The Virtqueue Descriptor Table}
content.tex +3 -0
index 1ca24c13f2d0..47239b877c6c 100644
@@ -51,6 +51,9 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
   an error from which it can't recover.
 \end{description}
 
+The \field{device status} field starts out as 0, and is reinitialized to 0 by
+the device during reset.
+
 \drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
 The driver MUST update \field{device status},
 setting bits to indicate the completed steps of the driver

content.tex \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev · line 79

Quoted 7 lines
content.tex +0 -1
@@ -71,7 +74,6 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
 \end{note}
 
 \devicenormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The device MUST initialize \field{device status} to 0 upon reset.
 
 The device MUST NOT consume buffers or send any used buffer
 notifications to the driver before DRIVER_OK.

Do we want to keep the part where it starts out as 0 here?

Quoted 46 lines
content.tex +20 -0
@@ -193,6 +195,26 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 terminology. Occasionally, the term event is used to refer to
 a notification or a receipt of a notification.
 
+\section{Device Reset}\label{sec:Basic Facilities of a Virtio Device / Device Reset}
+
+The driver may want to initiate a device reset at various times; notably,
+it is required to do so during device initialization and device cleanup.
+
+The mechanism used by the driver to initiate the reset is transport specific.
+
+\devicenormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+A device MUST reinitialize \field{device status} to 0 after receiving a reset.
+
+A device MUST NOT send notifications or interact with the queues after
+indicating completion of the reset by reinitializing \field{device status}
+to 0, until the driver re-initializes the device.
+
+\drivernormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+The driver SHOULD consider a driver-initiated reset complete when it
+reads \field{device status} as 0.
+
 \section{Device Configuration Space}\label{sec:Basic Facilities of a Virtio Device / Device Configuration Space}
 
 Device configuration space is generally used for rarely-changing or
Signature · 18 lines
2.26.2


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/

This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/

#5 lore raw
Quoted 27 lines · On Wed, 5 May 2021 09:20:45 -0400 "Michael S. Tsirkin" <[email protected]> wrote:
Quoted 26 lines · Cornelia Huck

Properly specify that the method for the driver to request a device reset is transport specific, and some action the device has to take.

---

Stefan, Halil: I did not apply your R-b due to the amount of changes.

v3 -> v4:
- moved device status 're-initialize to 0' clause that is now duplicated to an informal description
- more clarifications on when reset may be used and device requirements
- use \field{device status} consistently
RFC v2 -> v3:
- re-worded the "must not send notifications" clause to avoid guessing
- added a driver conformance clause on how a driver should find out when reset is complete
RFC -> RFC v2:
- moved reset spec to basic facilities

---
 conformance.tex |  2 ++
 content.tex     | 24 +++++++++++++++++++++++-
 2 files changed, 25 insertions(+), 1 deletion(-)

(...)

Quoted 17 lines
Quoted 17 lines
content.tex +3 -0
index 1ca24c13f2d0..47239b877c6c 100644
@@ -51,6 +51,9 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
   an error from which it can't recover.
 \end{description}
 
+The \field{device status} field starts out as 0, and is reinitialized to 0 by
+the device during reset.
+
 \drivernormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
 The driver MUST update \field{device status},
 setting bits to indicate the completed steps of the driver
@@ -71,7 +74,6 @@ \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev
 \end{note}
 
Quoted 7 lines

content.tex \section{\field{Device Status} Field}\label{sec:Basic Facilities of a Virtio Dev · line 79

Quoted 5 lines
content.tex +0 -1
 \devicenormative{\subsection}{Device Status Field}{Basic Facilities of a Virtio Device / Device Status Field}
-The device MUST initialize \field{device status} to 0 upon reset.
 
 The device MUST NOT consume buffers or send any used buffer
 notifications to the driver before DRIVER_OK.  

Do we want to keep the part where it starts out as 0 here?

Wouldn't that duplicate the statement in the 'Device Reset' normative section below?

Quoted 27 lines
Quoted 27 lines
content.tex +20 -0
@@ -193,6 +195,26 @@ \section{Notifications}\label{sec:Basic Facilities of a Virtio Device
 terminology. Occasionally, the term event is used to refer to
 a notification or a receipt of a notification.
 
+\section{Device Reset}\label{sec:Basic Facilities of a Virtio Device / Device Reset}
+
+The driver may want to initiate a device reset at various times; notably,
+it is required to do so during device initialization and device cleanup.
+
+The mechanism used by the driver to initiate the reset is transport specific.
+
+\devicenormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+A device MUST reinitialize \field{device status} to 0 after receiving a reset.
+
+A device MUST NOT send notifications or interact with the queues after
+indicating completion of the reset by reinitializing \field{device status}
+to 0, until the driver re-initializes the device.
+
+\drivernormative{\subsection}{Device Reset}{Basic Facilities of a Virtio Device / Device Reset}
+
+The driver SHOULD consider a driver-initiated reset complete when it
+reads \field{device status} as 0.
+
 \section{Device Configuration Space}\label{sec:Basic Facilities of a Virtio Device / Device Configuration Space}
 
Quoted 1 line

content.tex \section{Notifications}\label{sec:Basic Facilities of a Virtio Device · line 220

Quoted 1 line
content.tex +0 -0
 Device configuration space is generally used for rarely-changing or

This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting.

Subscribe: [email protected]
Unsubscribe: [email protected]
List help: [email protected]
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/