From: Paolo Bonzini <pbonzini@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 1/2] memory: make MemoryRegion alias migratable
Date: Tue, 30 Jul 2019 15:34:54 +0200 [thread overview]
Message-ID: <41ee4043-0f91-9bfa-f3f6-f85358250bb9@redhat.com> (raw)
In-Reply-To: <20190730152558.2e1aa23a@Igors-MacBook-Pro>
On 30/07/19 15:25, Igor Mammedov wrote:
> I'd guess you've meant RAMBlocks instead of memory regions, if that's it
> then yes, every alias pointing to RAM backed memory region will have
> RAMBlock that's points to aliased part of aliased memory region.
The question is just, does it break migration from old QEMU to new QEMU
on x86 (which has plenty of RAM-backed aliases)? If not, explain that
in the commit message or in a code comment.
Paolo
next prev parent reply other threads:[~2019-07-30 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 14:52 [Qemu-devel] [PATCH RFC 0/2] s390: stop abusing memory_region_allocate_system_memory() Igor Mammedov
2019-07-29 14:52 ` [Qemu-devel] [PATCH RFC 1/2] memory: make MemoryRegion alias migratable Igor Mammedov
2019-07-29 17:53 ` Dr. David Alan Gilbert
2019-07-30 13:25 ` Igor Mammedov
2019-07-30 13:34 ` Paolo Bonzini [this message]
2019-07-30 14:35 ` Igor Mammedov
2019-07-30 15:41 ` Dr. David Alan Gilbert
2019-07-29 14:52 ` [Qemu-devel] [PATCH RFC 2/2] s390: do not call memory_region_allocate_system_memory() multiple times Igor Mammedov
2019-07-29 14:58 ` [Qemu-devel] [PATCH RFC 0/2] s390: stop abusing memory_region_allocate_system_memory() Cornelia Huck
2019-07-30 15:22 ` [Qemu-devel] [qemu-s390x] " Christian Borntraeger
2019-07-30 15:49 ` Igor Mammedov
2019-08-02 8:04 ` David Hildenbrand
2019-08-02 8:23 ` David Hildenbrand
2019-08-02 8:26 ` David Hildenbrand
2019-08-02 8:29 ` Christian Borntraeger
2019-08-02 8:37 ` David Hildenbrand
2019-08-02 10:24 ` Christian Borntraeger
2019-08-02 9:18 ` Igor Mammedov
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=41ee4043-0f91-9bfa-f3f6-f85358250bb9@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.