On 06.07.23 16:03, Michael S. Tsirkin wrote:
On Thu, Jul 06, 2023 at 09:56:05AM +0200, David Hildenbrand wrote:
If there is no further feedback, I'll queue this myself shortly.
Stumbling over "x-ignore-shared" migration support for virtio-mem on
my todo list, I remember talking to Dave G. a while ago about how
ram_block_discard_range() in MAP_PIRVATE file mappings is possibly
harmful when the file is used somewhere else -- for example, with VM
templating in multiple VMs.
This series adds a warning to ram_block_discard_range() in that problematic
case and adds "x-ignore-shared" migration support for virtio-mem, which
is pretty straight-forward. The last patch also documents how VM templating
interacts with virtio-mem.
v1 -> v2:
- Pick up tags
- "virtio-mem: Support "x-ignore-shared" migration"
-> Fix spelling mistake
Reviewed-by: Michael S. Tsirkin <m...@redhat.com>
Thanks, I queued this to
https://github.com/davidhildenbrand/qemu.git mem-next
--
Cheers,
David / dhildenb
