[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [virtio] We need fixes to the csd and csprd before we can load them
Oh. We weren't careful about using Jira to track issues.On Tue, Mar 25, 2014 at 02:48:32PM -0400, Chet Ensign wrote:
> Hi Michael -
>
> On Tue, Mar 25, 2014 at 9:52 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>
>
> OK I have made the changes and uploaded the full zip files:
> https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/52588/
> virtio-v1.0-csd02.zip
> https://www.oasis-open.org/apps/org/workgroup/virtio/download.php/52589/
> virtio-v1.0-csprd02.zip
>
>
> Thanks - I'll look at them today and get back on track with them.
>
>
> Since these are minor technicalities, I assume that the rules
> do not require us to re-do the voting because of these
> changes.
>
> Please let me know otherwise.
>
>
> Nope - these are changes you are making at my direction. Acting as asst. TC
> Admin so to speak so no need for TC action on them at all.
>
>
>
> For draft 2 we are staying with tex as authoritative.
> In the new zip file there's now a README.txt file that
> gives some guidance on reading tex.
>
>
> Ok - I'll take a look. I'm sure that's ok.
>
>
>
> As was discussed, all specification is open to review
> and this is intentional.
> We'll discuss extending the review period once it starts.
>
>
> Ok, that'll wok.
>
>
> > 3) We need a comment resolution log from the TC for comments received in
> > csprd01
> >
> > Thanks - if you can send me those files when they are ready, I'll update
> the
> > ticket and we will continue to process the spec.
> >
> > Thanks & best,
> >
> > /chet
>
> OK here's a list with SVN commit numbers, dates, editors
> and change summary for each.
> Pls let me know if this is what's needed.
> I can also produce this in some other format if you wish (csv?).
>
>
> Here is what I need. I need a template like this filled out with the record of
> comments and decisions -> https://www.oasis-open.org/sites/www.oasis-open.org/
> files/Simple-charter-comment-log-template.xls
>
> Here is an example of one done for OData -> http://docs.oasis-open.org/odata/
> odata/v4.0/csprd01/odata-v4.0-csprd01-CommentResolutionLog.xls
>
> If you have all the comments in JIRA then you should be able to export the
> issues from there, clean them up a bit and have the log. The key here is the
> record of the comment tied to how the TC determined to handle it.
>
> I can show you how the JIRA export works under the new UI if you want. It took
> me a few minutes of poking to locate it.
>
> Best,
>
> /chet
We really should, and I'll do my best from now on.
In particular not all changes were entered in Jira,
and affected version and reporter are often not set.
I'll work on this list, hopefully tomorrow.
You also have the list of people who contributed
comments to acknowledge their contribution, don't you?
We wanted to put this in the document but though
about this too late, after TC voted on prd already.
> Check your work using the Support Request Submission Checklist at http://
>
>
>
> 327 & 13 Mar 2014 & Rusty Russell & { VIRTIO-60: avoid vring and
> VIRTIO_RING.
> These are never introduced, so use simpler names: virtq* for structures
> and VIRTIO_ for features.
> I added two notes about the old names, for helping people coming from
> the old spec.
> } \\
> \hline
> 326 & 13 Mar 2014 & Rusty Russell & { net: make num_buffers field
> compulsory (VIRTIO-86)
> } \\
> \hline
> 325 & 13 Mar 2014 & Rusty Russell & { block: deprecate FLUSH_OUT
> (VIRTIO-85)
> } \\
> \hline
> 324 & 13 Mar 2014 & Rusty Russell & { net: clean up mq definition, receive
> buf size (VIRTIO-84)
> 1) Instead of using N-1 everywhere, use N, and start receiveq etc at 1.
> This is less C like, but less confusing in english.
> 2) Weaken requirements for automatic steering to SHOULD, as otherwise
> we're insisting device record all flows forever.
> 3) Receive buffers must be able to hold data, so must be > header.
> Conflicts:
> content.tex
> } \\
> \hline
> 323 & 13 Mar 2014 & Rusty Russell & { VIRTIO-62: Explicit and specific.
> Avoid these words where they are redundant. This also lead me to
> notice that we were not consistent in the use of the term
> "device-specific configuration" in the PCI section, so cleaned that up
> too.
> } \\
> \hline
> 322 & 13 Mar 2014 & Rusty Russell & { VIRTIO-63: Make sure examples are
> marked clearly.
> } \\
> \hline
> 321 & 13 Mar 2014 & Rusty Russell & { VIRTIO-72: SHOULD/should
> } \\
> \hline
> 320 & 13 Mar 2014 & Rusty Russell & { VIRTIO-73: MAY/may.
> } \\
> \hline
> 319 & 13 Mar 2014 & Rusty Russell & { VIRTIO-74: required vs REQUIRED.
> Some really are clearest as they are, but most are changed to avoid
> confusion.
> } \\
> \hline
> 318 & 13 Mar 2014 & Rusty Russell & { VIRTIO-81: MUST vs must
> Clean up the remaining lowercase "musts". We actually introduce a
> new normative section in the balloon; for the rest we clarify them
> one way or another.
> } \\
> \hline
> 306 & 02 Mar 2014 & Michael S. Tsirkin & { fix rfc2119 reference
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> VIRTIO-68
> Cc: Patrick Durusau <patrick@durusau.net>
> } \\
> \hline
> 305 & 02 Mar 2014 & Michael S. Tsirkin & { VIRTIO-67: fix html redirects
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> 1. oasis switched to https
> 2. Red Hat is www.redhat.com
> Cc: Patrick Durusau <patrick@durusau.net>
> } \\
> \hline
> 304 & 02 Mar 2014 & Michael S. Tsirkin & { feedback: clarify device status
> bits
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> VIRTIO-70
> Cc: Patrick Durusau <patrick@durusau.net>
> } \\
> \hline
> 303 & 02 Mar 2014 & Michael S. Tsirkin & { legacy interface: move to
> terminology
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> VIRTIO-64
> Cc: Patrick Durusau <patrick@durusau.net
> } \\
> \hline
> 302 & 02 Mar 2014 & Michael S. Tsirkin & { introduction: add link to 0.9.5
> specification
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> this version replaces it, so it's a non normative reference.
> VIRTIO-69
> note: the link is added here but isn't used yet: will be used
> when we cleanup terminology definitions, by
> addressing VIRTIO-64
> Cc: Patrick Durusau <patrick@durusau.net
> } \\
> \hline
> 287 & 02 Mar 2014 & Michael S. Tsirkin & { drop /* LEGACY version was not
> little endian */
> Two issues with the comment:
> - it mixes legacy documentation in main part of the spec
> - it says what format *isn't* - instead of what it *is*
> Now that we have documented that LE can mean
> legacy endian, there's no need for the comment.
> Resolves issues:
> VIRTIO-58
> Change accepted on Virtio TC Meeting Minutes: Feb 25, 2014
> } \\
> \hline
> 280 & 26 Feb 2014 & Rusty Russell & { VIRTIO-45: Add a reserved ID for
> Timer/Clock device
> Just add a reserved ID for Timer/Clock device. There is no work
> on it yet but it is nice to have the ID which could be used safely
> in preliminary implementations.
> } \\
> \hline
> 279 & 26 Feb 2014 & Rusty Russell & { VIRTIO-28: Deprecate balloon device,
> add number for new one.
> } \\
> \hline
> 278 & 26 Feb 2014 & Rusty Russell & { Feedback: VIRTIO-77 Conformance
> clause.
> Now we have grouped all the normative statements, the conformance
> clauses for drivers and devices can simply reference them.
> } \\
> \hline
> 261 & 26 Feb 2014 & Rusty Russell & { Feedback: add old draft to normative
> references (VIRTIO-77)
> } \\
> \hline
> 260 & 26 Feb 2014 & Rusty Russell & { Feedback: use proper list in
> introduction (VIRTIO-82)
> Also avoid extra spacing before footnote markers.
> } \\
> \hline
> 258 & 26 Feb 2014 & Rusty Russell & { Feedback: Bug TAB-553 (VIRTIO-76)
> Haven't marked them non-normative yet, but it makes sense to put the header
> in an appendix.
> } \\
> \hline
> 257 & 26 Feb 2014 & Rusty Russell & { Feedback: TAB-555 Bad sub-sectioning
> (VIRTIO-80)
> } \\
> \hline
> 256 & 26 Feb 2014 & Rusty Russell & { Feedback: TAB-557 Spelling errors,
> etc (VIRTIO-75)
> } \\
> \hline
> 249 & 13 Feb 2014 & Cornelia Huck & { ccw: padding annotations
> Remove __packed__ annotation from all ccw structures that don't need it,
> and make the length requirements explicit for those that do.
> This is the part of the patch to resolve VIRTIO-56 that had been missed.
> } \\
> \hline
> 244 & 12 Feb 2014 & Rusty Russell & { VIRTIO-55: Add a reserved ID for GPU
> devices
> As existing work on virtio-gpu is using device ID 16, reflect this in
> the spec. This closes out VIRTIO-55.
> As per minutes:
> \url{https://lists.oasis-open.org/archives/virtio/201402/
> msg00121.html}
> } \\
> \hline
> 167 & 09 Dec 2013 & Michael S. Tsirkin & { net: document
> VIRTIO_NET_F_MAC_ADDR
> VIRTIO-50
> commit f058954d131e3dc73058778ad23b241a235ae8e1
> virtio-spec: set mac address by a new vq command
> Approved Dec 3, 2013
> } \\
> \hline
> 166 & 09 Dec 2013 & Michael S. Tsirkin & { net: add _F_MQ support
> VIRTIO-49
> Includes git commits:
> 3c600996f641614d3720c94dd52155aaaba670fa
> virtio-spec: fix two typos
> commit 67023431c8796bc430ec0a79b15bab57e2e0f1f6
> virtio-spec: virtio network device multiqueue support
> commit a02d91f8729b4a333d525015d22138a86ce9b644
> net: add note that you can defer rx queue init until mq enable.
> Approved Dec 3, 2013
> } \\
> \hline
> >
> >
> > --
> >
> > /chet
> > ----------------
> > Chet Ensign
> > Director of Standards Development and TC Administration
> > OASIS: Advancing open standards for the information society
> > http://www.oasis-open.org
> >
> > Primary: +1 973-996-2298
> > Mobile: +1 201-341-1393
> >
> > Check your work using the Support Request Submission Checklist at http://
> > www.oasis-open.org/committees/download.php/47248/
> > tc-admin-submission-checklist.html
> >
> > TC Administration information and support is available at http://
> > www.oasis-open.org/resources/tcadmin
> >
> > Follow OASIS on:
> > LinkedIn: http://linkd.in/OASISopen
> > Twitter: http://twitter.com/OASISopen
> > Facebook: http://facebook.com/oasis.open
>
>
>
>
> --
>
> /chet
> ----------------
> Chet Ensign
> Director of Standards Development and TC Administration
> OASIS: Advancing open standards for the information society
> http://www.oasis-open.org
>
> Primary: +1 973-996-2298
> Mobile: +1 201-341-1393
>
> www.oasis-open.org/committees/download.php/47248/
> tc-admin-submission-checklist.html
>
> TC Administration information and support is available at http://
> www.oasis-open.org/resources/tcadmin
>
> Follow OASIS on:
> LinkedIn: http://linkd.in/OASISopen
> Twitter: http://twitter.com/OASISopen
> Facebook: http://facebook.com/oasis.open
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]