diff options
| author | Luiz Capitulino <lcapitulino@redhat.com> | 2011-07-29 14:26:33 -0300 |
|---|---|---|
| committer | Luiz Capitulino <lcapitulino@redhat.com> | 2011-09-15 16:39:32 -0300 |
| commit | 1dfb4dd993f7122353fb2894f09dfcba894cd7d5 (patch) | |
| tree | 72559b694b482e5b0dc1f77faf96aa31d3678f64 /hw/virtio.c | |
| parent | bff046f86b4f8970c722c3bc3e32173b8000e716 (diff) | |
Replace the VMSTOP macros with a proper state type
Today, when notifying a VM state change with vm_state_notify(),
we pass a VMSTOP macro as the 'reason' argument. This is not ideal
because the VMSTOP macros tell why qemu stopped and not exactly
what the current VM state is.
One example to demonstrate this problem is that vm_start() calls
vm_state_notify() with reason=0, which turns out to be VMSTOP_USER.
This commit fixes that by replacing the VMSTOP macros with a proper
state type called RunState.
Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Diffstat (limited to 'hw/virtio.c')
| -rw-r--r-- | hw/virtio.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/hw/virtio.c b/hw/virtio.c index 13aa0faf27..74ab79e6b5 100644 --- a/hw/virtio.c +++ b/hw/virtio.c @@ -837,7 +837,7 @@ void virtio_cleanup(VirtIODevice *vdev) g_free(vdev); } -static void virtio_vmstate_change(void *opaque, int running, int reason) +static void virtio_vmstate_change(void *opaque, int running, RunState state) { VirtIODevice *vdev = opaque; bool backend_run = running && (vdev->status & VIRTIO_CONFIG_S_DRIVER_OK); |