virtio-spec: Add virtio-mem device specification
v2 cover virtio-spec: Add virtio-mem device specification
Add the specification for virtio-mem devices. The Linux driver is part of v5.8-rc1. The latest QEMU implementation (v4) can be found at [1].
[1] https://lkml.kernel.org/r/[email protected]
v1 -> v2:
- Adapt to configuration layout change (block_size is now 64 bit)
- Some minor rephrasings
David Hildenbrand (3):
conformance: make driver conformance list easier to read and maintain
conformance: Reference RPMB Driver Conformance
Add virtio-mem device specification
conformance.tex | 47 ++++- content.tex | 1 + virtio-mem.tex | 448 ++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 493 insertions(+), 3 deletions(-) create mode 100644 virtio-mem.tex
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/
PATCH v2 1/3 conformance: make driver conformance list easier to read and maintain
Let's define it just like the device conformance list.
--- conformance.tex | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-)
conformance.tex +11 -1
@@ -15,7 +15,17 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \begin{itemize} \item Clause \ref{sec:Conformance / Driver Conformance}. \item One of clauses \ref{sec:Conformance / Driver Conformance / PCI Driver Conformance}, \ref{sec:Conformance / Driver Conformance / MMIO Driver Conformance} or \ref{sec:Conformance / Driver Conformance / Channel I/O Driver Conformance}. - \item One of clauses \ref{sec:Conformance / Driver Conformance / Network Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Block Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Console Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Entropy Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Traditional Memory Balloon Driver Conformance}, \ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or \ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}. + \item One of clauses +\ref{sec:Conformance / Driver Conformance / Network Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Block Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Console Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Entropy Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Traditional Memory Balloon Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or +\ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}. \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}. \end{itemize} \item[Device] A device MUST conform to four conformance clauses:
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/
PATCH v2 2/3 conformance: Reference RPMB Driver Conformance
In reply to David HildenbrandWe forgot to reference the driver conformance.
--- conformance.tex | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
conformance.tex +2 -1
@@ -24,7 +24,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, -\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or +\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / RPMB Driver Conformance} or \ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}. \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}. \end{itemize}
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/
Re: [virtio-comment] [PATCH v2 2/3] conformance: Reference RPMB Driver Conformance
Quoted 5 lines · David Hildenbrand
We forgot to reference the driver conformance.
Reviewed-by Cornelia Huck <[email protected]>Cc Yang Huang <[email protected]>Signed-off-by David Hildenbrand <[email protected]>
Quoted 18 lines
--- conformance.tex | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)conformance.tex +2
-1@@ -24,7 +24,8 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \ref{sec:Conformance / Driver Conformance / SCSI Host Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, -\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance} or +\ref{sec:Conformance / Driver Conformance / Socket Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / RPMB Driver Conformance} or \ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}. \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}. \end{itemize}
Signature · 17 lines
Alex Bennée 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/
PATCH v2 3/3 Add virtio-mem device specification
In reply to David HildenbrandThe virtio memory device provides and manages a memory region in guest physical address space. This memory region is partitioned into memory blocks of fixed size that can either be in the state plugged or unplugged.
Specify the device configuration, initialization, and operation. Introduce PLUG, UNPLUG, UNPLUG ALL and STATE requests.
--- conformance.tex | 38 +++- content.tex | 1 + virtio-mem.tex | 448 ++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 483 insertions(+), 4 deletions(-) create mode 100644 virtio-mem.tex
conformance.tex +34 -4
@@ -25,8 +25,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \ref{sec:Conformance / Driver Conformance / Input Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Crypto Driver Conformance}, \ref{sec:Conformance / Driver Conformance / Socket Driver Conformance}, -\ref{sec:Conformance / Driver Conformance / RPMB Driver Conformance} or -\ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance}. +\ref{sec:Conformance / Driver Conformance / RPMB Driver Conformance}, +\ref{sec:Conformance / Driver Conformance / IOMMU Driver Conformance} or +\ref{sec:Conformance / Driver Conformance / Memory Driver Conformance}. \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}. \end{itemize} \item[Device] A device MUST conform to four conformance clauses:
@@ -43,8 +44,9 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \ref{sec:Conformance / Device Conformance / Input Device Conformance}, \ref{sec:Conformance / Device Conformance / Crypto Device Conformance}, \ref{sec:Conformance / Device Conformance / Socket Device Conformance}, -\ref{sec:Conformance / Device Conformance / RPMB Device Conformance} or -\ref{sec:Conformance / Device Conformance / IOMMU Device Conformance}. +\ref{sec:Conformance / Device Conformance / RPMB Device Conformance}, +\ref{sec:Conformance / Device Conformance / IOMMU Device Conformance}, or +\ref{sec:Conformance / Device Conformance / Memory Device Conformance}. \item Clause \ref{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance}. \end{itemize} \end{description}
@@ -231,6 +233,20 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \item \ref{drivernormative:Device Types / IOMMU Device / Device operations / Fault reporting} \end{itemize} +\conformance{\subsection}{Memory Driver Conformance}\label{sec:Conformance / Driver Conformance / Memory Driver Conformance} + +A memory driver MUST conform to the following normative statements: + +\begin{itemize} +\item \ref{drivernormative:Device Types / Memory Device / Device configuration layout} +\item \ref{drivernormative:Device Types / Memory Device / Device Initialization} +\item \ref{drivernormative:Device Types / Memory Device / Device Operation} +\item \ref{drivernormative:Device Types / Memory Device / Device Operation / PLUG request} +\item \ref{drivernormative:Device Types / Memory Device / Device Operation / UNPLUG request} +\item \ref{drivernormative:Device Types / Memory Device / Device Operation / UNPLUG ALL request} +\item \ref{drivernormative:Device Types / Memory Device / Device Operation / STATE request} +\end{itemize} + \conformance{\section}{Device Conformance}\label{sec:Conformance / Device Conformance} A device MUST conform to the following normative statements:
@@ -419,6 +435,20 @@ \section{Conformance Targets}\label{sec:Conformance / Conformance Targets} \item \ref{devicenormative:Device Types / IOMMU Device / Device operations / Fault reporting} \end{itemize} +\conformance{\subsection}{Memory Device Conformance}\label{sec:Conformance / Device Conformance / Memory Device Conformance} + +A memory device MUST conform to the following normative statements: + +\begin{itemize} +\item \ref{devicenormative:Device Types / Memory Device / Device configuration layout} +\item \ref{devicenormative:Device Types / Memory Device / Device Initialization} +\item \ref{devicenormative:Device Types / Memory Device / Device Operation} +\item \ref{devicenormative:Device Types / Memory Device / Device Operation / PLUG request} +\item \ref{devicenormative:Device Types / Memory Device / Device Operation / UNPLUG request} +\item \ref{devicenormative:Device Types / Memory Device / Device Operation / UNPLUG ALL request} +\item \ref{devicenormative:Device Types / Memory Device / Device Operation / STATE request} +\end{itemize} + \conformance{\section}{Legacy Interface: Transitional Device and Transitional Driver Conformance}\label{sec:Conformance / Legacy Interface: Transitional Device and Transitional Driver Conformance} A conformant implementation MUST be either transitional or non-transitional, see \ref{intro:Legacy
content.tex +1 -0
@@ -6062,6 +6062,7 @@ \subsubsection{Legacy Interface: Framing Requirements}\label{sec:Device \input{virtio-fs.tex} \input{virtio-rpmb.tex} \input{virtio-iommu.tex} +\input{virtio-mem.tex} \chapter{Reserved Feature Bits}\label{sec:Reserved Feature Bits}
virtio-mem.tex new file +448 -0
448 lines not on this page · raw message
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/
Quoted 5 lines · David Hildenbrand
Add the specification for virtio-mem devices. The Linux driver is part of v5.8-rc1. The latest QEMU implementation (v4) can be found at [1].
Quoted 8 lines
v1 -> v2:
- Adapt to configuration layout change (block_sizeis now 64 bit)
- Some minor rephrasingsDavid Hildenbrand (3):
conformance: make driver conformance list easier to read and maintain
conformance: Reference RPMB Driver Conformance
Add virtio-mem device specification
Gentle ping, I'll be opening a github issue now but wait a little bit longer until replying with "Fixes:".
Signature · 20 lines
Thanks, David / dhildenb 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/
Quoted 14 lines · David Hildenbrand
Add the specification for virtio-mem devices. The Linux driver is part of v5.8-rc1. The latest QEMU implementation (v4) can be found at [1].
[1] https://lkml.kernel.org/r/[email protected]
v1 -> v2:
- Adapt to configuration layout change (block_sizeis now 64 bit)
- Some minor rephrasingsDavid Hildenbrand (3):
conformance: make driver conformance list easier to read and maintain
conformance: Reference RPMB Driver Conformance
Add virtio-mem device specification
Quoted 6 lines
conformance.tex | 47 ++++- content.tex | 1 + virtio-mem.tex | 448 ++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 493 insertions(+), 3 deletions(-) create mode 100644 virtio-mem.tex
Okay, v2 has been around for more than a month without comments requesting a change. If there are no further comments, I request voting for inclusion.
Signature · 20 lines
Thanks, David / dhildenb 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/