From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ivshmem: Fix unplug of device "ivshmem-plain"
Date: Mon, 1 Oct 2018 11:42:59 +0200 [thread overview]
Message-ID: <55838024-13d8-792c-24f1-f9b4f62b59f2@redhat.com> (raw)
In-Reply-To: <20180926163709.22876-1-armbru@redhat.com>
On 26/09/2018 18:37, Markus Armbruster wrote:
> Commit 2aece63c8a "hostmem: detect host backend memory is being used
> properly" fixed "ivshmem-plain" to reject memory backends that are
> already in use, and to block their deletion while in use. Two bugs
> escaped review:
>
> * New ivshmem_plain_exit() fails to call ivshmem_exit(). This breaks
> unplug. Reproducer: migration after unplug still fails with
> "Migration is disabled when using feature 'peer mode' in device
> 'ivshmem'".
>
> * It failed to update legacy "ivshmem". Harmless, because it creates
> the memory backend itself, and nothing else should use it.
>
> Fix by moving the two host_memory_backend_set_mapped() calls into
> ivshmem_common_realize() and ivshmem_exit(), guarded by s->hostmem.
>
> Fixes: 2aece63c8a9d2c3a8ff41d2febc4cdeff2633331
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> hw/misc/ivshmem.c | 14 +++++---------
> 1 file changed, 5 insertions(+), 9 deletions(-)
>
> diff --git a/hw/misc/ivshmem.c b/hw/misc/ivshmem.c
> index 6febbabcaa..8cb17b9dd4 100644
> --- a/hw/misc/ivshmem.c
> +++ b/hw/misc/ivshmem.c
> @@ -911,6 +911,7 @@ static void ivshmem_common_realize(PCIDevice *dev, Error **errp)
> IVSHMEM_DPRINTF("using hostmem\n");
>
> s->ivshmem_bar2 = host_memory_backend_get_memory(s->hostmem);
> + host_memory_backend_set_mapped(s->hostmem, true);
> } else {
> Chardev *chr = qemu_chr_fe_get_driver(&s->server_chr);
> assert(chr);
> @@ -993,6 +994,10 @@ static void ivshmem_exit(PCIDevice *dev)
> vmstate_unregister_ram(s->ivshmem_bar2, DEVICE(dev));
> }
>
> + if (s->hostmem) {
> + host_memory_backend_set_mapped(s->hostmem, false);
> + }
> +
> if (s->peers) {
> for (i = 0; i < s->nb_peers; i++) {
> close_peer_eventfds(s, i);
> @@ -1101,14 +1106,6 @@ static void ivshmem_plain_realize(PCIDevice *dev, Error **errp)
> }
>
> ivshmem_common_realize(dev, errp);
> - host_memory_backend_set_mapped(s->hostmem, true);
> -}
> -
> -static void ivshmem_plain_exit(PCIDevice *pci_dev)
> -{
> - IVShmemState *s = IVSHMEM_COMMON(pci_dev);
> -
> - host_memory_backend_set_mapped(s->hostmem, false);
> }
>
> static void ivshmem_plain_class_init(ObjectClass *klass, void *data)
> @@ -1117,7 +1114,6 @@ static void ivshmem_plain_class_init(ObjectClass *klass, void *data)
> PCIDeviceClass *k = PCI_DEVICE_CLASS(klass);
>
> k->realize = ivshmem_plain_realize;
> - k->exit = ivshmem_plain_exit;
> dc->props = ivshmem_plain_properties;
> dc->vmsd = &ivshmem_plain_vmsd;
> }
>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks for the fix!
Paolo
parent reply other threads:[~2018-10-01 9:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20180926163709.22876-1-armbru@redhat.com>]
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=55838024-13d8-792c-24f1-f9b4f62b59f2@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@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).