OASIS Virtual I/O Device (VIRTIO) TC

Hi, I've taken a quick look at the TAB feedback as far as it pertains to ccw/s390. A lot of it had already been fixed, here are two more patches with further changes. Cornelia Huck (2): ccw: Further use of RFC2119 language. Fix S390 normative references. content.tex 6 +++--- introduction.tex 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) -- 1.7.9.5

As pointed out in TAB-539 and TAB-540: - Add an URL to the documents. (Unfortunately, there is no link that always points to the latest version.) - State that we include any future revisions as well. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> --- introduction.tex 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/introduction.tex b/introduction.tex index 2830f30..313e30f 100644 --- a/introduction.tex +++ b/introduction.tex @@ -40,8 +40,8 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "S egin{longtable}{l p{5in}} phantomsectionlabel{intro:rfc2119} extbf{[RFC2119]} & S. Bradner, Key words for use in RFCs to Indicate Requirement Levels,
ewlineurl{ http://www.ietf.org/rfc/rfc2119.txt} , March 1997\ - phantomsectionlabel{intro:S390 PoP} extbf{[S390 PoP]} & z/Architecture Principles of Operation,
ewline IBM Publication SA22-7832\ - phantomsectionlabel{intro:S390 Common I/O} extbf{[S390 Common I/O]} & ESA/390 Common I/O-Device and Self-Description,
ewline IBM Publication SA22-7204\ + phantomsectionlabel{intro:S390 PoP} extbf{[S390 PoP]} & z/Architecture Principles of Operation, IBM Publication SA22-7832,
ewlineurl{ http://publibfi.boulder.ibm.com/epubs/pdf/dz9zr009.pdf} , and any future revisions\ + phantomsectionlabel{intro:S390 Common I/O} extbf{[S390 Common I/O]} & ESA/390 Common I/O-Device and Self-Description, IBM Publication SA22-7204,
ewlineurl{ http://publibfp.dhe.ibm.com/cgi-bin/bookmgr/BOOKS/dz9ar501/CCONTENTS} , and any future revisions\ end{longtable} section{Structure Specifications} -- 1.7.9.5

Some more instances of MAY and SHOULD, as reported in TAB comments TAB-548 and TAB-550. Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com> --- content.tex 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content.tex b/content.tex index ed2c3fa..96c4fc8 100644 --- a/content.tex +++ b/content.tex @@ -2194,7 +2194,7 @@ for the devices are contained, starting at bit_nr, one bit per virtqueue of the device. Bit numbers start at the left, i.e. the most significant bit in the first byte is assigned the bit number 0. isc contains the I/O interruption subclass to be used for the adapter -I/O interrupt. It may be different from the isc used by the proxy +I/O interrupt. It MAY be different from the isc used by the proxy virtio-ccw device's subchannel. No padding is added at the end of the structure, it is exactly 25 bytes in length. @@ -2283,10 +2283,10 @@ The device MUST ignore bits 0-31 (counting from the left) of GPR2. This aligns passing the subchannel ID with the way it is passed for the existing I/O instructions. -Host cookie is an optional per-virtqueue 64 bit value that can be +Host cookie is an optional per-virtqueue 64 bit value that MAY be used by the hypervisor to speed up the notification execution. For each notification, the output value is returned in GPR2 and -should be passed in GPR4 for the next notification: +SHOULD be passed in GPR4 for the next notification: egin{lstlisting} info->cookie = do_notify(schid, -- 1.7.9.5