2019-01-03 17:10:02 +03:00
|
|
|
/*
|
|
|
|
|
* Virtio balloon PCI Bindings
|
|
|
|
|
*
|
|
|
|
|
* Copyright IBM, Corp. 2007
|
|
|
|
|
* Copyright (c) 2009 CodeSourcery
|
|
|
|
|
*
|
|
|
|
|
* Authors:
|
|
|
|
|
* Anthony Liguori <aliguori@us.ibm.com>
|
|
|
|
|
* Paul Brook <paul@codesourcery.com>
|
|
|
|
|
*
|
|
|
|
|
* Contributions after 2012-01-13 are licensed under the terms of the
|
|
|
|
|
* GNU GPL, version 2 or (at your option) any later version.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include "qemu/osdep.h"
|
|
|
|
|
|
2022-03-21 18:30:25 +03:00
|
|
|
#include "hw/virtio/virtio-pci.h"
|
2019-08-12 08:23:51 +03:00
|
|
|
#include "hw/qdev-properties.h"
|
2019-01-03 17:10:02 +03:00
|
|
|
#include "hw/virtio/virtio-balloon.h"
|
|
|
|
|
#include "qapi/error.h"
|
2019-05-23 17:35:07 +03:00
|
|
|
#include "qemu/module.h"
|
2020-09-03 23:43:22 +03:00
|
|
|
#include "qom/object.h"
|
2019-01-03 17:10:02 +03:00
|
|
|
|
|
|
|
|
typedef struct VirtIOBalloonPCI VirtIOBalloonPCI;
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
|
* virtio-balloon-pci: This extends VirtioPCIProxy.
|
|
|
|
|
*/
|
|
|
|
|
#define TYPE_VIRTIO_BALLOON_PCI "virtio-balloon-pci-base"
|
2020-09-01 00:07:33 +03:00
|
|
|
DECLARE_INSTANCE_CHECKER(VirtIOBalloonPCI, VIRTIO_BALLOON_PCI,
|
|
|
|
|
TYPE_VIRTIO_BALLOON_PCI)
|
2019-01-03 17:10:02 +03:00
|
|
|
|
|
|
|
|
struct VirtIOBalloonPCI {
|
|
|
|
|
VirtIOPCIProxy parent_obj;
|
|
|
|
|
VirtIOBalloon vdev;
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void virtio_balloon_pci_realize(VirtIOPCIProxy *vpci_dev, Error **errp)
|
|
|
|
|
{
|
|
|
|
|
VirtIOBalloonPCI *dev = VIRTIO_BALLOON_PCI(vpci_dev);
|
|
|
|
|
DeviceState *vdev = DEVICE(&dev->vdev);
|
|
|
|
|
|
2021-02-03 20:18:31 +03:00
|
|
|
vpci_dev->class_code = PCI_CLASS_OTHERS;
|
qdev: Convert uses of qdev_set_parent_bus() with Coccinelle
In addition to the qdev_create() patterns converted so far, we have a
qdev_set_parent_bus() pattern. Mostly when we embed a device in a
parent device rather than allocating it on the heap.
This pattern also puts devices in the dangerous "no QOM parent, but
plugged into bus" state I explained in recent commit "qdev: New
qdev_new(), qdev_realize(), etc."
Apply same solution: convert to qdev_realize(). Coccinelle script:
@@
expression dev, bus, errp;
symbol true;
@@
- qdev_set_parent_bus(DEVICE(dev), bus);
...
- object_property_set_bool(OBJECT(dev), true, "realized", errp);
+ qdev_realize(DEVICE(dev), bus, errp);
@ depends on !(file in "qdev-monitor.c") && !(file in "hw/core/qdev.c")@
expression dev, bus, errp;
symbol true;
@@
- qdev_set_parent_bus(dev, bus);
...
- object_property_set_bool(OBJECT(dev), true, "realized", errp);
+ qdev_realize(dev, bus, errp);
@@
expression dev, bus;
symbol true;
@@
- qdev_set_parent_bus(DEVICE(dev), bus);
...
- qdev_init_nofail(DEVICE(dev));
+ qdev_realize(DEVICE(dev), bus, &error_fatal);
Unconverted uses of qdev_set_parent_bus() remain. They'll be
converted later in this series.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20200610053247.1583243-12-armbru@redhat.com>
[Also convert new hw/virtio/vhost-user-vsock-pci.c]
2020-06-10 08:32:00 +03:00
|
|
|
qdev_realize(vdev, BUS(&vpci_dev->bus), errp);
|
2019-01-03 17:10:02 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void virtio_balloon_pci_class_init(ObjectClass *klass, void *data)
|
|
|
|
|
{
|
|
|
|
|
DeviceClass *dc = DEVICE_CLASS(klass);
|
|
|
|
|
VirtioPCIClass *k = VIRTIO_PCI_CLASS(klass);
|
|
|
|
|
PCIDeviceClass *pcidev_k = PCI_DEVICE_CLASS(klass);
|
|
|
|
|
k->realize = virtio_balloon_pci_realize;
|
|
|
|
|
set_bit(DEVICE_CATEGORY_MISC, dc->categories);
|
|
|
|
|
pcidev_k->vendor_id = PCI_VENDOR_ID_REDHAT_QUMRANET;
|
|
|
|
|
pcidev_k->device_id = PCI_DEVICE_ID_VIRTIO_BALLOON;
|
|
|
|
|
pcidev_k->revision = VIRTIO_PCI_ABI_VERSION;
|
|
|
|
|
pcidev_k->class_id = PCI_CLASS_OTHERS;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static void virtio_balloon_pci_instance_init(Object *obj)
|
|
|
|
|
{
|
|
|
|
|
VirtIOBalloonPCI *dev = VIRTIO_BALLOON_PCI(obj);
|
|
|
|
|
|
|
|
|
|
virtio_instance_init_common(obj, &dev->vdev, sizeof(dev->vdev),
|
|
|
|
|
TYPE_VIRTIO_BALLOON);
|
|
|
|
|
object_property_add_alias(obj, "guest-stats", OBJECT(&dev->vdev),
|
qom: Drop parameter @errp of object_property_add() & friends
The only way object_property_add() can fail is when a property with
the same name already exists. Since our property names are all
hardcoded, failure is a programming error, and the appropriate way to
handle it is passing &error_abort.
Same for its variants, except for object_property_add_child(), which
additionally fails when the child already has a parent. Parentage is
also under program control, so this is a programming error, too.
We have a bit over 500 callers. Almost half of them pass
&error_abort, slightly fewer ignore errors, one test case handles
errors, and the remaining few callers pass them to their own callers.
The previous few commits demonstrated once again that ignoring
programming errors is a bad idea.
Of the few ones that pass on errors, several violate the Error API.
The Error ** argument must be NULL, &error_abort, &error_fatal, or a
pointer to a variable containing NULL. Passing an argument of the
latter kind twice without clearing it in between is wrong: if the
first call sets an error, it no longer points to NULL for the second
call. ich9_pm_add_properties(), sparc32_ledma_realize(),
sparc32_dma_realize(), xilinx_axidma_realize(), xilinx_enet_realize()
are wrong that way.
When the one appropriate choice of argument is &error_abort, letting
users pick the argument is a bad idea.
Drop parameter @errp and assert the preconditions instead.
There's one exception to "duplicate property name is a programming
error": the way object_property_add() implements the magic (and
undocumented) "automatic arrayification". Don't drop @errp there.
Instead, rename object_property_add() to object_property_try_add(),
and add the obvious wrapper object_property_add().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20200505152926.18877-15-armbru@redhat.com>
[Two semantic rebase conflicts resolved]
2020-05-05 18:29:22 +03:00
|
|
|
"guest-stats");
|
2019-01-03 17:10:02 +03:00
|
|
|
object_property_add_alias(obj, "guest-stats-polling-interval",
|
|
|
|
|
OBJECT(&dev->vdev),
|
qom: Drop parameter @errp of object_property_add() & friends
The only way object_property_add() can fail is when a property with
the same name already exists. Since our property names are all
hardcoded, failure is a programming error, and the appropriate way to
handle it is passing &error_abort.
Same for its variants, except for object_property_add_child(), which
additionally fails when the child already has a parent. Parentage is
also under program control, so this is a programming error, too.
We have a bit over 500 callers. Almost half of them pass
&error_abort, slightly fewer ignore errors, one test case handles
errors, and the remaining few callers pass them to their own callers.
The previous few commits demonstrated once again that ignoring
programming errors is a bad idea.
Of the few ones that pass on errors, several violate the Error API.
The Error ** argument must be NULL, &error_abort, &error_fatal, or a
pointer to a variable containing NULL. Passing an argument of the
latter kind twice without clearing it in between is wrong: if the
first call sets an error, it no longer points to NULL for the second
call. ich9_pm_add_properties(), sparc32_ledma_realize(),
sparc32_dma_realize(), xilinx_axidma_realize(), xilinx_enet_realize()
are wrong that way.
When the one appropriate choice of argument is &error_abort, letting
users pick the argument is a bad idea.
Drop parameter @errp and assert the preconditions instead.
There's one exception to "duplicate property name is a programming
error": the way object_property_add() implements the magic (and
undocumented) "automatic arrayification". Don't drop @errp there.
Instead, rename object_property_add() to object_property_try_add(),
and add the obvious wrapper object_property_add().
Signed-off-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20200505152926.18877-15-armbru@redhat.com>
[Two semantic rebase conflicts resolved]
2020-05-05 18:29:22 +03:00
|
|
|
"guest-stats-polling-interval");
|
2019-01-03 17:10:02 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
static const VirtioPCIDeviceTypeInfo virtio_balloon_pci_info = {
|
|
|
|
|
.base_name = TYPE_VIRTIO_BALLOON_PCI,
|
|
|
|
|
.generic_name = "virtio-balloon-pci",
|
|
|
|
|
.transitional_name = "virtio-balloon-pci-transitional",
|
|
|
|
|
.non_transitional_name = "virtio-balloon-pci-non-transitional",
|
|
|
|
|
.instance_size = sizeof(VirtIOBalloonPCI),
|
|
|
|
|
.instance_init = virtio_balloon_pci_instance_init,
|
|
|
|
|
.class_init = virtio_balloon_pci_class_init,
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
static void virtio_balloon_pci_register(void)
|
|
|
|
|
{
|
|
|
|
|
virtio_pci_types_register(&virtio_balloon_pci_info);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
type_init(virtio_balloon_pci_register)
|