Michal Privoznik 9985f62b51 qemu: Wire up MEMORY_DEVICE_SIZE_CHANGE event ... As advertised in previous commit, this event is delivered to us when virtio-mem module changes the allocation inside the guest. It comes with one attribute - size - which holds the new size of the virtio-mem (well, allocated size), in bytes. Mind you, this is not necessarily the same number as 'requested size'. It almost certainly will be when sizing the memory up, but it might not be when sizing the memory down - the guest kernel might be unable to free some blocks. This current size is reported in the domain XML as an output element only. Signed-off-by: Michal Privoznik <mprivozn@redhat.com> Reviewed-by: Ján Tomko <jtomko@redhat.com>		2021-10-01 11:04:47 +02:00
..
c	qemu: Wire up MEMORY_DEVICE_SIZE_CHANGE event	2021-10-01 11:04:47 +02:00
polkit	meson: examples: build and install example files	2020-08-03 09:27:06 +02:00
sh	meson: examples: build and install example files	2020-08-03 09:27:06 +02:00
systemtap	examples: Use GLib event loop impl in events.stp	2020-08-21 11:34:23 +01:00
xml	test_driver: Introduce testIOThreadInfo and generate IOThread infos	2021-09-23 13:41:11 +02:00
meson.build	meson: examples: build and install example files	2020-08-03 09:27:06 +02:00