All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@linux.vnet.ibm.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: linuxppc-dev@lists.ozlabs.org,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
Subject: Re: [PATCH slof v2] virtio: Fix vring allocation
Date: Fri, 13 Mar 2015 11:25:48 +0100	[thread overview]
Message-ID: <20150313112548.06e2c378@oc7435384737.ibm.com> (raw)
In-Reply-To: <1426239723-25789-1-git-send-email-aik@ozlabs.ru>

On Fri, 13 Mar 2015 20:42:03 +1100
Alexey Kardashevskiy <aik@ozlabs.ru> wrote:

> The value returned by virtio_vring_size() is used to allocate memory
> for vring. The used descriptor list (array of vring_used_elem) is
> counted by the header - vring_used struct - is not.
> 
> This fixes virtio_vring_size() to return the correct size.
> At the moment rings are quite small (256) and allocated with
> 4096 alignment, this is why we have not been having issues with
> this so far.
> 
> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
> ---
> Changes:
> v2:
> * remove magic numbers
> ---
>  lib/libvirtio/virtio.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/libvirtio/virtio.c b/lib/libvirtio/virtio.c
> index b010796..f9c00a6 100644
> --- a/lib/libvirtio/virtio.c
> +++ b/lib/libvirtio/virtio.c
> @@ -32,8 +32,10 @@
>   */
>  unsigned long virtio_vring_size(unsigned int qsize)
>  {
> -	return VQ_ALIGN(sizeof(struct vring_desc) * qsize + 2 * (2 + qsize))
> -		+ VQ_ALIGN(sizeof(struct vring_used_elem) * qsize);
> +	return VQ_ALIGN(sizeof(struct vring_desc) * qsize +
> +                        sizeof(struct vring_avail) + sizeof(uint16_t) * qsize) +
> +               VQ_ALIGN(sizeof(struct vring_used) +
> +                        sizeof(struct vring_used_elem) * qsize);
>  }

Reviewed-by: Thomas Huth <thuth@linux.vnet.ibm.com>

That should be at least ok for the current status that we support in
SLOF. I think I might have written the original version of that
function with a very old version of the virtio spec (v0.8.10), when
ther was no "used_event" event field in the struct vring_avail defined
yet.
But if SLOF ever supports VIRTIO_F_EVENT_IDX, we've got to keep in mind
to add some additional bytes here, too.

 Thomas

      parent reply	other threads:[~2015-03-13 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  8:40 [PATCH slof] virtio: Fix vring allocation Alexey Kardashevskiy
2015-03-13  9:19 ` Nikunj A Dadhania
2015-03-13  9:42   ` [PATCH slof v2] " Alexey Kardashevskiy
2015-03-13 10:14     ` Nikunj A Dadhania
2015-03-13 10:25     ` Thomas Huth [this message]

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=20150313112548.06e2c378@oc7435384737.ibm.com \
    --to=thuth@linux.vnet.ibm.com \
    --cc=aik@ozlabs.ru \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nikunj@linux.vnet.ibm.com \
    /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.