* Igor Mammedov (imamm...@redhat.com) wrote:
> On Tue, 30 Jul 2019 15:34:54 +0200
> Paolo Bonzini wrote:
>
> > 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 wi
On Tue, 30 Jul 2019 15:34:54 +0200
Paolo Bonzini wrote:
> 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 ali
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
On Mon, 29 Jul 2019 18:53:15 +0100
"Dr. David Alan Gilbert" wrote:
> * Igor Mammedov (imamm...@redhat.com) wrote:
> > use qemu_ram_alloc_from_ptr() to create aliased RAMBlock
> > to the part of original memory region.
> >
> > Signed-off-by: Igor Mammedov
> > ---
> > exec.c | 7 ---
> > m
* Igor Mammedov (imamm...@redhat.com) wrote:
> use qemu_ram_alloc_from_ptr() to create aliased RAMBlock
> to the part of original memory region.
>
> Signed-off-by: Igor Mammedov
> ---
> exec.c | 7 ---
> memory.c | 5 +
> 2 files changed, 9 insertions(+), 3 deletions(-)
>
> diff --git
use qemu_ram_alloc_from_ptr() to create aliased RAMBlock
to the part of original memory region.
Signed-off-by: Igor Mammedov
---
exec.c | 7 ---
memory.c | 5 +
2 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/exec.c b/exec.c
index 3e78de3b8f..daef0cd54f 100644
--- a/exec
