From: David Hildenbrand <david@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v22 QEMU 3/5] virtio-balloon: Replace free page hinting references to 'report' with 'hint'
Date: Mon, 27 Apr 2020 17:10:57 +0200 [thread overview]
Message-ID: <829a7d06-d5f4-1d82-32b9-744603288d84@redhat.com> (raw)
In-Reply-To: <CAKgT0Uckr4uN=WCvGtp5GtXRZjfR+x1BR7L5b=RvnT7CHwtsMw@mail.gmail.com>
On 27.04.20 17:08, Alexander Duyck wrote:
> On Mon, Apr 27, 2020 at 1:15 AM David Hildenbrand <david@redhat.com> wrote:
>>
>> There is only one wrong comment remaining I think. Something like
>>
>> diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
>> index a1d6fb52c8..1b2127c04c 100644
>> --- a/hw/virtio/virtio-balloon.c
>> +++ b/hw/virtio/virtio-balloon.c
>> @@ -554,8 +554,8 @@ static void virtio_balloon_free_page_stop(VirtIOBalloon *s)
>> */
>> qemu_mutex_lock(&s->free_page_lock);
>> /*
>> - * The guest hasn't done the reporting, so host sends a notification
>> - * to the guest to actively stop the reporting.
>> + * The guest isn't done with hinting, so the host sends a notification
>> + * to the guest to actively stop the hinting.
>
> I'll probably tweak it slightly and drop the "with". So the comment will read:
> /*
> * The guest isn't done hinting, so host sends a notification
I always feel like "so host sends" sounds wrong ("the host"). But I am
not a native speaker.
> * to the guest to actively stop the hinting.
> */
>
> There is one other spot left which is support for migration. The name
> for the VMStateDescription is
> "virtio-balloon-device/free-page-report". I am assuming I cannot
> rename that. Otherwise all other references to report on the balloon
> interface refer to reporting errors from what I can tell.
Yeah, that has to stay for migration to keep working.
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-04-27 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 16:50 [PATCH v22 QEMU 0/5] virtio-balloon: add support for page poison reporting and free page reporting Alexander Duyck
2020-04-24 16:50 ` [PATCH v22 QEMU 1/5] linux-headers: Update to allow renaming of free_page_report_cmd_id Alexander Duyck
2020-04-24 16:50 ` [PATCH v22 QEMU 2/5] linux-headers: update to contain virito-balloon free page reporting Alexander Duyck
2020-04-24 16:50 ` [PATCH v22 QEMU 3/5] virtio-balloon: Replace free page hinting references to 'report' with 'hint' Alexander Duyck
2020-04-27 8:15 ` David Hildenbrand
2020-04-27 15:08 ` Alexander Duyck
2020-04-27 15:10 ` David Hildenbrand [this message]
2020-04-27 15:57 ` Alexander Duyck
2020-04-27 15:59 ` David Hildenbrand
2020-04-24 16:50 ` [PATCH v22 QEMU 4/5] virtio-balloon: Implement support for page poison reporting feature Alexander Duyck
2020-04-27 8:18 ` David Hildenbrand
2020-04-24 16:50 ` [PATCH v22 QEMU 5/5] virtio-balloon: Provide an interface for free page reporting Alexander Duyck
2020-04-27 8:21 ` David Hildenbrand
2020-04-27 8:21 ` [PATCH v22 QEMU 0/5] virtio-balloon: add support for page poison reporting and " David Hildenbrand
2020-04-27 15:11 ` [virtio-dev] " Alexander Duyck
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=829a7d06-d5f4-1d82-32b9-744603288d84@redhat.com \
--to=david@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=virtio-dev@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;
as well as URLs for NNTP newsgroup(s).