From: "Andreas Färber" <afaerber@suse.de>
To: Bandan Das <bsd@redhat.com>,
qemu-devel@nongnu.org, Michael Tsirkin <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
qemu-stable <qemu-stable@nongnu.org>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH for-1.7] pci: unregister vmstate_pcibus on unplug
Date: Tue, 19 Nov 2013 13:51:58 +0100 [thread overview]
Message-ID: <528B5EEE.5000705@suse.de> (raw)
In-Reply-To: <jpgwqkluori.fsf@redhat.com>
Am 06.11.2013 23:52, schrieb Bandan Das:
>
> PCIBus registers a vmstate during init. Unregister it upon
> removal/unplug.
>
> Signed-off-by: Bandan Das <bsd@redhat.com>
Michael, this patch looks good for 1.7 to me, are you planning to still
pick it up? Only one small comment below.
Cc: qemu-stable@nongnu.org
> ---
> Note that I didn't add a instance_init to register vmstate (yet)
> due to concerns expressed by Andreas that we shouldn't be registering
> global state there.
What's happening here is the following: instance_init does in fact not
register anything, but vmstate_unregister() becomes a no-op loop if the
vmsd+opaque combo is not registered, so it is safe. The registration
happens in pci_bus_new() / pci_bus_new_inplace(), which I believe all
PCI buses to date inside QEMU use, i.e. after instance_init, so in
practice unregistering will not be no-op.
> hw/pci/pci.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/hw/pci/pci.c b/hw/pci/pci.c
> index a98c8a0..63ef7ce 100644
> --- a/hw/pci/pci.c
> +++ b/hw/pci/pci.c
> @@ -47,6 +47,7 @@ static void pcibus_dev_print(Monitor *mon, DeviceState *dev, int indent);
> static char *pcibus_get_dev_path(DeviceState *dev);
> static char *pcibus_get_fw_dev_path(DeviceState *dev);
> static int pcibus_reset(BusState *qbus);
> +static void pci_bus_finalize(Object *obj);
It may be nicer to avoid the prototype by moving the new
pci_bus_finalize() above pci_bus_info. But since what counts is the fix
to avoid segfaults during migration on access to a dangling opaque
pointer after hot-unplug of a PCI-PCI bridge,
Reviewed-by: Andreas Färber <afaerber@suse.de>
Thanks,
Andreas
>
> static Property pci_props[] = {
> DEFINE_PROP_PCI_DEVFN("addr", PCIDevice, devfn, -1),
> @@ -73,6 +74,7 @@ static const TypeInfo pci_bus_info = {
> .name = TYPE_PCI_BUS,
> .parent = TYPE_BUS,
> .instance_size = sizeof(PCIBus),
> + .instance_finalize = pci_bus_finalize,
> .class_init = pci_bus_class_init,
> };
>
> @@ -401,6 +403,12 @@ int pci_bus_num(PCIBus *s)
> return s->parent_dev->config[PCI_SECONDARY_BUS];
> }
>
> +static void pci_bus_finalize(Object *obj)
> +{
> + PCIBus *bus = PCI_BUS(obj);
> + vmstate_unregister(NULL, &vmstate_pcibus, bus);
> +}
> +
> static int get_pci_config_device(QEMUFile *f, void *pv, size_t size)
> {
> PCIDevice *s = container_of(pv, PCIDevice, config);
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-11-19 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 22:52 [Qemu-devel] [PATCH] pci: unregister vmstate_pcibus on unplug Bandan Das
2013-11-19 12:51 ` Andreas Färber [this message]
2013-11-19 13:56 ` [Qemu-devel] [PATCH for-1.7] " Michael S. Tsirkin
2013-11-19 17:03 ` Bandan Das
2013-11-19 17:33 ` Andreas Färber
2013-11-19 17:44 ` Paolo Bonzini
2013-11-19 17:50 ` Bandan Das
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=528B5EEE.5000705@suse.de \
--to=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=bsd@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).