Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.vnet.ibm.com>
Cc: virtio@lists.oasis-open.org, virtio-dev@lists.oasis-open.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio] Re: [PATCH 2/5] consistency: clean up stale  wording for v1.1 terms
Date: Tue, 10 Apr 2018 11:30:07 +0200	[thread overview]
Message-ID: <20180410113007.44377586.cohuck@redhat.com> (raw)
In-Reply-To: <1523300322-21989-3-git-send-email-pasic@linux.vnet.ibm.com>

On Mon,  9 Apr 2018 20:58:39 +0200
Halil Pasic <pasic@linux.vnet.ibm.com> wrote:

> Occasionally we still use used and available ring instead of Device and
> Driver Area respectively. Same goes for descriptor table with the
> difference that depending on the context we need either Descriptor Area
> or descriptor ring.
> 
> Let's clean these up, at least where the cleanup is trivial.
> 
> Signed-off-by: Halil Pasic <pasic@linux.vnet.ibm.com>
> ---
>  content.tex     |   14 +++++++-------
>  packed-ring.tex |   10 ++++++----
>  2 files changed, 13 insertions(+), 11 deletions(-)
> 

> -\drivernormative{\subsection}{The Virtqueue Descriptor Table}{Basic Facilities of a Virtio Device / PAcked Virtqueues / The Virtqueue Descriptor Table}
> +\drivernormative{\subsection}{The Virtqueue Descriptor Ring}{Basic Facilities of a Virtio Device / PAcked Virtqueues / The Virtqueue Descriptor Ring}

While you're touching it anyway: s/PAcked/Packed/ ? (Probably needs a
change in conformance.tex as well.)

>  A driver MUST NOT change a descriptor unless it observes
>  the VIRTQ_DESC_F_USED bit in its \field{flags} being changed.
>  A driver MUST NOT change a descriptor after changing

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 


  reply	other threads:[~2018-04-10  9:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 18:58 [virtio] [PATCH 0/5] fixes and tweaks for virtio v1.1 Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 1/5] packed-ring: fix used descriptors but meant buffers Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 2/5] consistency: clean up stale wording for v1.1 terms Halil Pasic
2018-04-10  9:30   ` Cornelia Huck [this message]
2018-04-10 10:04     ` [virtio] " Halil Pasic
2018-04-10 10:06       ` Cornelia Huck
2018-04-09 18:58 ` [virtio] [PATCH 3/5] packed-packed: fix supplying buffers description Halil Pasic
2018-04-09 18:58 ` [virtio] [PATCH 4/5] packed-ring: reposition drivernormative on driver notifications Halil Pasic
2018-04-09 19:51   ` Paolo Bonzini
2018-04-10 10:25     ` Halil Pasic
2018-04-10 11:05       ` Paolo Bonzini
2018-04-10 14:59         ` Halil Pasic
2018-04-20 15:45           ` Paolo Bonzini
2018-04-20 15:59           ` Michael S. Tsirkin
2018-04-20 16:22             ` Halil Pasic
2018-04-20 16:28               ` Michael S. Tsirkin
2018-04-09 18:58 ` [virtio] [PATCH 5/5] packed-ring: tweak driver code example Halil Pasic
2018-04-20 15:00 ` [virtio] [PATCH 0/5] fixes and tweaks for virtio v1.1 Halil Pasic
2018-04-27 16:07   ` Halil Pasic

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=20180410113007.44377586.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=virtio-dev@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /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