From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Leonardo Bras" <leobras@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peng Tao" <tao.peng@linux.alibaba.com>,
"Mario Casquero" <mcasquer@redhat.com>
Subject: Re: [PATCH v2 0/4] virtio-mem: Support "x-ignore-shared" migration
Date: Fri, 7 Jul 2023 14:21:17 +0200 [thread overview]
Message-ID: <271fc385-08a0-deda-f8ba-a5a4171543be@redhat.com> (raw)
In-Reply-To: <20230706100303-mutt-send-email-mst@kernel.org>
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 <mst@redhat.com>
Thanks, I queued this to
https://github.com/davidhildenbrand/qemu.git mem-next
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2023-07-07 12:22 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 7:56 [PATCH v2 0/4] virtio-mem: Support "x-ignore-shared" migration David Hildenbrand
2023-07-06 7:56 ` [PATCH v2 1/4] softmmu/physmem: Warn with ram_block_discard_range() on MAP_PRIVATE file mapping David Hildenbrand
2023-07-06 8:10 ` Juan Quintela
2023-07-06 8:31 ` David Hildenbrand
2023-07-06 13:20 ` Juan Quintela
2023-07-06 13:23 ` David Hildenbrand
2023-07-06 8:49 ` David Hildenbrand
2023-10-18 3:02 ` Xiaoyao Li
2023-10-18 7:42 ` David Hildenbrand
2023-10-18 9:02 ` Xiaoyao Li
2023-10-18 9:26 ` David Hildenbrand
2023-10-18 16:27 ` Xiaoyao Li
2023-10-19 8:26 ` David Hildenbrand
2023-10-19 9:26 ` Xiaoyao Li
2023-10-19 9:43 ` David Hildenbrand
2023-07-06 7:56 ` [PATCH v2 2/4] virtio-mem: Skip most of virtio_mem_unplug_all() without plugged memory David Hildenbrand
2023-07-06 8:15 ` Juan Quintela
2023-07-06 8:38 ` David Hildenbrand
2023-07-06 13:27 ` Juan Quintela
2023-07-06 7:56 ` [PATCH v2 3/4] migration/ram: Expose ramblock_is_ignored() as migrate_ram_is_ignored() David Hildenbrand
2023-07-06 8:16 ` Juan Quintela
2023-07-06 7:56 ` [PATCH v2 4/4] virtio-mem: Support "x-ignore-shared" migration David Hildenbrand
2023-07-06 11:06 ` Juan Quintela
2023-07-06 11:27 ` David Hildenbrand
2023-07-06 11:59 ` Juan Quintela
2023-07-06 14:03 ` [PATCH v2 0/4] " Michael S. Tsirkin
2023-07-07 12:21 ` David Hildenbrand [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=271fc385-08a0-deda-f8ba-a5a4171543be@redhat.com \
--to=david@redhat.com \
--cc=leobras@redhat.com \
--cc=mcasquer@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=tao.peng@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).