From: Paolo Bonzini <pbonzini@redhat.com>
To: Zenghui Yu <yuzenghui@huawei.com>, qemu-devel@nongnu.org
Cc: cohuck@redhat.com, kwankhede@nvidia.com,
alex.williamson@redhat.com, qemu-arm@nongnu.org,
wanghaibin.wang@huawei.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] memory: Skip dirty tracking for un-migratable memory regions
Date: Mon, 16 Nov 2020 19:22:07 +0100 [thread overview]
Message-ID: <5f5cc5a8-c5e4-4a69-5fdd-7020459d9d17@redhat.com> (raw)
In-Reply-To: <20201116132210.1730-1-yuzenghui@huawei.com>
On 16/11/20 14:22, Zenghui Yu wrote:
> It makes no sense to track dirty pages for those un-migratable memory
> regions (e.g., Memory BAR region of the VFIO PCI device) and doing so
> will potentially lead to some unpleasant issues during migration [1].
>
> Skip dirty tracking for those regions by evaluating if the region is
> migratable before setting dirty_log_mask (DIRTY_MEMORY_MIGRATION).
>
> [1] https://lists.gnu.org/archive/html/qemu-devel/2020-11/msg03757.html
>
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
> softmmu/memory.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/softmmu/memory.c b/softmmu/memory.c
> index 71951fe4dc..aa393f1bb0 100644
> --- a/softmmu/memory.c
> +++ b/softmmu/memory.c
> @@ -1806,7 +1806,10 @@ bool memory_region_is_ram_device(MemoryRegion *mr)
> uint8_t memory_region_get_dirty_log_mask(MemoryRegion *mr)
> {
> uint8_t mask = mr->dirty_log_mask;
> - if (global_dirty_log && (mr->ram_block || memory_region_is_iommu(mr))) {
> + RAMBlock *rb = mr->ram_block;
> +
> + if (global_dirty_log && ((rb && qemu_ram_is_migratable(rb)) ||
> + memory_region_is_iommu(mr))) {
> mask |= (1 << DIRTY_MEMORY_MIGRATION);
> }
> return mask;
>
Queued, thanks.
Paolo
prev parent reply other threads:[~2020-11-16 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 13:22 [PATCH] memory: Skip dirty tracking for un-migratable memory regions Zenghui Yu
2020-11-16 17:46 ` Cornelia Huck
2020-11-16 18:22 ` Paolo Bonzini [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=5f5cc5a8-c5e4-4a69-5fdd-7020459d9d17@redhat.com \
--to=pbonzini@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kwankhede@nvidia.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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).