qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: David Hildenbrand <david@redhat.com>,
	Alexander Duyck <alexander.duyck@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Wei Wang <wei.w.wang@intel.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v1 3/3] virtio-balloon: unref the iothread when unrealizing
Date: Mon, 18 May 2020 18:01:42 +0200	[thread overview]
Message-ID: <8454c9a5-63c2-e145-574c-606abb2d9475@redhat.com> (raw)
In-Reply-To: <299d4475-bfd4-34b7-749f-ed11076d23c3@redhat.com>

+Stefan/Paolo in case they have a better clue.

On 5/18/20 5:41 PM, David Hildenbrand wrote:
> On 18.05.20 17:35, Alexander Duyck wrote:
>> On Mon, May 18, 2020 at 1:37 AM David Hildenbrand <david@redhat.com> wrote:
>>>
>>> We took a reference when realizing, so let's drop that reference when
>>> unrealizing.
>>>
>>> Fixes: c13c4153f76d ("virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT")
>>> Cc: Wei Wang <wei.w.wang@intel.com>
>>> Cc: Alexander Duyck <alexander.duyck@gmail.com>
>>> Cc: Michael S. Tsirkin <mst@redhat.com>
>>> Cc: Philippe Mathieu-Daudé <philmd@redhat.com>
>>> Signed-off-by: David Hildenbrand <david@redhat.com>
>>> ---
>>>   hw/virtio/virtio-balloon.c | 1 +
>>>   1 file changed, 1 insertion(+)
>>>
>>> diff --git a/hw/virtio/virtio-balloon.c b/hw/virtio/virtio-balloon.c
>>> index a4fcf2d777..3f8fc50be0 100644
>>> --- a/hw/virtio/virtio-balloon.c
>>> +++ b/hw/virtio/virtio-balloon.c
>>> @@ -820,6 +820,7 @@ static void virtio_balloon_device_unrealize(DeviceState *dev)
>>>
>>>       if (s->free_page_bh) {
>>>           qemu_bh_delete(s->free_page_bh);
>>> +        object_unref(OBJECT(s->iothread));
>>>           virtio_balloon_free_page_stop(s);
>>>           precopy_remove_notifier(&s->free_page_report_notify);
>>>       }
>>
>> I'm not entirely sure about this order of operations. It seems like it
>> would make more sense to remove the notifier, stop the hinting, delete
>> the bh, and then release the IO thread.
> 
> This is the reverse order of the steps in
> virtio_balloon_device_realize(). And I guess it should be fine. The
> notifier cannot really be active/trigger while we are removing devices
> (cannot happen with concurrent migration). After qemu_bh_delete(), the
> iothread is effectively unused.
> 
> I am unsure about many things regarding free page hinting (e.g., if the
> virtio_balloon_free_page_stop() is of any use while we are ripping out
> the device and it will be gone in a second).
> 



  reply	other threads:[~2020-05-18 16:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  8:37 [PATCH v1 0/3] virtio-balloon: free page hinting fixes David Hildenbrand
2020-05-18  8:37 ` [PATCH v1 1/3] virtio-balloon: fix free page hinting without an iothread David Hildenbrand
2020-05-18  9:18   ` Philippe Mathieu-Daudé
2020-05-18 15:01   ` Alexander Duyck
2020-05-18 15:28     ` David Hildenbrand
2020-05-18  8:37 ` [PATCH v1 2/3] virtio-balloon: fix free page hinting check on unrealize David Hildenbrand
2020-05-18  9:19   ` Philippe Mathieu-Daudé
2020-05-18 15:20   ` Alexander Duyck
2020-05-18 15:51     ` David Hildenbrand
2020-05-18  8:37 ` [PATCH v1 3/3] virtio-balloon: unref the iothread when unrealizing David Hildenbrand
2020-05-18  9:19   ` Philippe Mathieu-Daudé
2020-05-18 15:35   ` Alexander Duyck
2020-05-18 15:41     ` David Hildenbrand
2020-05-18 16:01       ` Philippe Mathieu-Daudé [this message]
2020-05-18 17:55       ` Alexander Duyck
2020-05-18  9:20 ` [PATCH v1 0/3] virtio-balloon: free page hinting fixes Philippe Mathieu-Daudé
2020-05-18  9:36   ` David Hildenbrand

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=8454c9a5-63c2-e145-574c-606abb2d9475@redhat.com \
    --to=philmd@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=david@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --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).