qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	qemu-devel <qemu-devel@nongnu.org>,
	David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] virtio-balloon: correct used length
Date: Wed, 24 Nov 2021 15:58:22 +0800	[thread overview]
Message-ID: <CACGkMEsGX6y9cppLoGGsNtoJvbw4TLBVo2V0TFLOGr-JybXA-w@mail.gmail.com> (raw)
In-Reply-To: <20211124020118-mutt-send-email-mst@kernel.org>

On Wed, Nov 24, 2021 at 3:03 PM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Wed, Nov 24, 2021 at 12:32:55PM +0800, Jason Wang wrote:
> > Spec said:
> >
> > "and len the total of bytes written into the buffer."
> >
> > For inflateq, deflateq and statsq, we don't process in_sg so the used
> > length should be zero. For free_page_vq, though the free pages are
> > supplied via in_sgs, zero used length should still be fine since
> > anyway driver is expected to use the length in this case and it
> > simplifies the error handling path.
> >
> > Signed-off-by: Jason Wang <jasowang@redhat.com>
>
> I think for free page vq the point is that the pages are
> zeroed by hypervisor, so we must set used len accordingly. No?

I may miss something, I think it is used for clearing the dirty
bitmaps to avoid migrating unused pages, the zeroing is not needed.

Thanks

>
> > ---
> >  hw/virtio/virtio-balloon.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
> > index c6962fcbfe..3e52daa793 100644
> > --- a/hw/virtio/virtio-balloon.c
> > +++ b/hw/virtio/virtio-balloon.c
> > @@ -231,7 +231,7 @@ static void balloon_stats_poll_cb(void *opaque)
> >          return;
> >      }
> >
> > -    virtqueue_push(s->svq, s->stats_vq_elem, s->stats_vq_offset);
> > +    virtqueue_push(s->svq, s->stats_vq_elem, 0);
> >      virtio_notify(vdev, s->svq);
> >      g_free(s->stats_vq_elem);
> >      s->stats_vq_elem = NULL;
> > @@ -438,7 +438,7 @@ static void virtio_balloon_handle_output(VirtIODevice *vdev, VirtQueue *vq)
> >              memory_region_unref(section.mr);
> >          }
> >
> > -        virtqueue_push(vq, elem, offset);
> > +        virtqueue_push(vq, elem, 0);
> >          virtio_notify(vdev, vq);
> >          g_free(elem);
> >          virtio_balloon_pbp_free(&pbp);
> > @@ -549,7 +549,7 @@ static bool get_free_page_hints(VirtIOBalloon *dev)
> >      }
> >
> >  out:
> > -    virtqueue_push(vq, elem, 1);
> > +    virtqueue_push(vq, elem, 0);
> >      g_free(elem);
> >      return ret;
> >  }
> > --
> > 2.25.1
>



  reply	other threads:[~2021-11-24  8:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24  4:32 [PATCH] virtio-balloon: correct used length Jason Wang
2021-11-24  7:03 ` Michael S. Tsirkin
2021-11-24  7:58   ` Jason Wang [this message]
2021-11-24  8:25     ` Michael S. Tsirkin
2021-11-24  8:28       ` Jason Wang
2021-11-24  8:32         ` Jason Wang
2021-11-24  9:17           ` Michael S. Tsirkin

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=CACGkMEsGX6y9cppLoGGsNtoJvbw4TLBVo2V0TFLOGr-JybXA-w@mail.gmail.com \
    --to=jasowang@redhat.com \
    --cc=david@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).