diff options
| author | David Hildenbrand | 2021-09-29 18:24:45 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2021-10-02 08:43:21 +0200 |
| commit | 77ae2302ae167aa840d5a3aa489f7958db7c1426 (patch) | |
| tree | dc000490d17523911684fc9d305cb1899ea871f5 /python | |
| parent | qapi: Include qom-path in MEMORY_DEVICE_SIZE_CHANGE qapi events (diff) | |
| download | qemu-77ae2302ae167aa840d5a3aa489f7958db7c1426.tar.gz qemu-77ae2302ae167aa840d5a3aa489f7958db7c1426.tar.xz qemu-77ae2302ae167aa840d5a3aa489f7958db7c1426.zip | |
monitor: Rate-limit MEMORY_DEVICE_SIZE_CHANGE qapi events per device
We want to rate-limit MEMORY_DEVICE_SIZE_CHANGE events per device,
otherwise we can lose some events for devices. We can now use the
qom-path to reliably map an event to a device and make rate-limiting
device-aware.
This was noticed by starting a VM with two virtio-mem devices that each
have a requested size > 0. The Linux guest will initialize both devices
in parallel, resulting in losing MEMORY_DEVICE_SIZE_CHANGE events for
one of the devices.
Fixes: 722a3c783ef4 ("virtio-pci: Send qapi events when the virtio-mem size changes")
Suggested-by: Markus Armbruster <armbru@redhat.com>
Reviewed-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20210929162445.64060-4-david@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'python')
0 files changed, 0 insertions, 0 deletions