All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Philipp Hahn <hahn@univention.de>
Cc: virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [ERRATUM?] 5.5.6.3 Memory Statistics: 6 -> 10 byte
Date: Sun, 26 May 2019 15:35:36 -0400	[thread overview]
Message-ID: <20190526153404-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1988b2f8-04cc-0e15-17a1-55b9958a328b@univention.de>

On Fri, May 24, 2019 at 11:35:47AM +0200, Philipp Hahn wrote:
> Hello Michael,
> 
> Am 24.05.19 um 05:39 schrieb Michael S. Tsirkin:
> > On Thu, May 23, 2019 at 02:51:48PM +0200, Philipp Hahn wrote:
> >> quoting
> >> <https://docs.oasis-open.org/virtio/virtio/v1.1/cs01/virtio-v1.1-cs01.html#x1-2930003>:
> >>
> >>> Within the buffer, statistics are an array of 6-byte entries. 
> >>                                                 ^
> >>> Each statistic consists of a 16 bit tag and a 64 bit value.
> >> ...
> >>> struct virtio_balloon_stat { 
> >> ...
> >>>         le16 tag; 
> >>>         le64 val; 
> >>> } __attribute__((packed));
> >>
> >> If my calculation is right that is a (16 + 64) = 80 bits which is a
> >> 10-byte sized entry - not 6-byte.
> > 
> > 
> > Agreed. Want to open a github issue?
> 
> Sure, here it is: <https://github.com/oasis-tcs/virtio-spec/issues/45>
> 
> Patch attached and also available from
> <https://github.com/univention/virtio-spec/commit/609dbbbe71fc9143c2849d2c9c2d481ec178ce30>
> 
> Philipp

> >From 609dbbbe71fc9143c2849d2c9c2d481ec178ce30 Mon Sep 17 00:00:00 2001
> Message-Id: <609dbbbe71fc9143c2849d2c9c2d481ec178ce30.1558690397.git.hahn@univention.de>
> From: Philipp Hahn <hahn@univention.de>
> Date: Fri, 24 May 2019 11:29:17 +0200
> Subject: [PATCH] Issue #45: Fix Memory Statistics structure size
> 
> > Within the buffer, statistics are an array of 6-byte entries.
>                                                 ^
> > Each statistic consists of a 16 bit tag and a 64 bit value.
> ...
> > struct virtio_balloon_stat {
> ...
> >         le16 tag;
> >         le64 val;
> > } __attribute__((packed));
> 
> If my calculation is right that is a (16 + 64) = 80 bits which is a
> 10-byte sized entry - not 6-byte.
> ---
>  content.tex | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/content.tex b/content.tex
> index 193b6e1..dee1f28 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -4766,7 +4766,7 @@ \subsubsection{Memory Statistics}\label{sec:Device Types / Memory Balloon Device
>    subsequent request) and consumes the statistics.
>  \end{enumerate}
>  
> -  Within the buffer, statistics are an array of 6-byte entries.
> +  Within the buffer, statistics are an array of 10-byte entries.
>    Each statistic consists of a 16 bit
>    tag and a 64 bit value. All statistics are optional and the
>    driver chooses which ones to supply. To guarantee backwards
> -- 
> 2.11.0
> 
> 

Thanks!
Unfortunately neither form gets the patch into our mailing
list archives as required by the TC bylaws.
See https://lists.oasis-open.org/archives/virtio-comment/201905/msg00014.html
for what got archived.

The thing to do is to include the patch inline in the message body.
Thanks and sorry for the run-around!




> 
> 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: virtio-comment-subscribe@lists.oasis-open.org
> Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
> List help: virtio-comment-help@lists.oasis-open.org
> 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: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
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/


  reply	other threads:[~2019-05-26 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-23 12:51 [virtio-comment] [ERRATUM?] 5.5.6.3 Memory Statistics: 6 -> 10 byte Philipp Hahn
2019-05-24  3:39 ` Michael S. Tsirkin
2019-05-24  9:35   ` Philipp Hahn
2019-05-26 19:35     ` Michael S. Tsirkin [this message]
2019-05-27  6:49       ` Philipp Hahn

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=20190526153404-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=hahn@univention.de \
    --cc=virtio-comment@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.