From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: mpe@ellerman.id.au, Jason Wang <jasowang@redhat.com>,
Wei Wang <wei.w.wang@intel.com>,
qemu-devel@nongnu.org,
Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH 1/2] virito-balloon: process all in sgs for free_page_vq
Date: Thu, 25 Nov 2021 17:11:05 +0100 [thread overview]
Message-ID: <d162f85f-214b-3d4b-c860-47b3367e7099@redhat.com> (raw)
In-Reply-To: <20211125110724-mutt-send-email-mst@kernel.org>
On 25.11.21 17:09, Michael S. Tsirkin wrote:
> On Thu, Nov 25, 2021 at 09:28:59AM +0100, David Hildenbrand wrote:
>> On 25.11.21 03:20, Jason Wang wrote:
>>> We only process the first in sg which may lead to the bitmap of the
>>> pages belongs to following sgs were not cleared. This may result more
>>> pages to be migrated. Fixing this by process all in sgs for
>>> free_page_vq.
>>>
>>> Signed-off-by: Jason Wang <jasowang@redhat.com>
>>> ---
>>> hw/virtio/virtio-balloon.c | 7 +++++--
>>> 1 file changed, 5 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
>>> index c6962fcbfe..17de2558cb 100644
>>> --- a/hw/virtio/virtio-balloon.c
>>> +++ b/hw/virtio/virtio-balloon.c
>>> @@ -510,6 +510,7 @@ static bool get_free_page_hints(VirtIOBalloon *dev)
>>> VirtIODevice *vdev = VIRTIO_DEVICE(dev);
>>> VirtQueue *vq = dev->free_page_vq;
>>> bool ret = true;
>>> + int i;
>>>
>>> while (dev->block_iothread) {
>>> qemu_cond_wait(&dev->free_page_cond, &dev->free_page_lock);
>>> @@ -544,8 +545,10 @@ static bool get_free_page_hints(VirtIOBalloon *dev)
>>> }
>>>
>>> if (elem->in_num && dev->free_page_hint_status == FREE_PAGE_HINT_S_START) {
>>> - qemu_guest_free_page_hint(elem->in_sg[0].iov_base,
>>> - elem->in_sg[0].iov_len);
>>> + for (i = 0; i < elem->in_num; i++) {
>>> + qemu_guest_free_page_hint(elem->in_sg[i].iov_base,
>>> + elem->in_sg[i].iov_len);
>>> + }
>>> }
>>>
>>> out:
>>>
>>
>> Yes, but:
>>
>> 1. Linux never used more than one
>> 2. QEMU never consumed more than one
>>
>> The spec states:
>>
>> "(b) The driver maps a series of pages and adds them to the free_page_vq
>> as individual scatter-gather input buffer entries."
>>
>> However, the spec was written by someone else (Alex) as the code was
>> (Wei). The code was there first.
>>
>> I don't particularly care what to adjust (code or spec). However, to me
>> it feels more like the spec is slightly wrong and it was intended like
>> the code is by the original code author.
>>
>> But then again, I don't particularly care :)
>
> Original QEMU side code had several bugs so, that's another one.
> Given nothing too bad happens if guest submits too many S/Gs,
> and given the spec also has a general chapter suggesting devices
> are flexible in accepting a single buffer split to multiple S/Gs,
> I'm inclined to accept the patch.
Yeah, as I said, I don't particularly care. It's certainly an "easy change".
Acked-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2021-11-25 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 2:20 [PATCH 1/2] virito-balloon: process all in sgs for free_page_vq Jason Wang
2021-11-25 2:20 ` [PATCH 2/2] virtio-balloon: correct used length Jason Wang
2021-11-25 16:14 ` Michael S. Tsirkin
2021-11-26 2:45 ` Jason Wang
2021-11-26 7:36 ` Michael S. Tsirkin
2021-11-29 2:48 ` Jason Wang
2021-11-25 8:28 ` [PATCH 1/2] virito-balloon: process all in sgs for free_page_vq David Hildenbrand
2021-11-25 16:09 ` Michael S. Tsirkin
2021-11-25 16:11 ` David Hildenbrand [this message]
2021-11-26 1:21 ` Wang, Wei W
2021-11-26 1:42 ` Michael S. Tsirkin
2021-11-26 2:31 ` Jason Wang
2021-11-26 2:40 ` Wang, Wei W
2021-11-26 2:43 ` Jason Wang
2021-11-25 8:34 ` Philippe Mathieu-Daudé
2021-11-25 16:10 ` Michael S. Tsirkin
2021-11-26 2:42 ` Jason Wang
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=d162f85f-214b-3d4b-c860-47b3367e7099@redhat.com \
--to=david@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=jasowang@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wei.w.wang@intel.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 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).