From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [Qemu-devel] [PATCH 3/4] exec, memory: Call to xen_modified_memory. Date: Tue, 17 Jul 2012 16:37:37 +0300 Message-ID: <50056AA1.9010004__38944.3710133948$1342532377$gmane$org@redhat.com> References: <1342531805-29894-1-git-send-email-anthony.perard@citrix.com> <1342531805-29894-4-git-send-email-anthony.perard@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1342531805-29894-4-git-send-email-anthony.perard@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Anthony PERARD Cc: Anthony Liguori , Luiz Capitulino , Stefano Stabellini , QEMU-devel , Xen Devel List-Id: xen-devel@lists.xenproject.org On 07/17/2012 04:30 PM, Anthony PERARD wrote: > This patch add some calls to xen_modified_memory to notify Xen about dirtybits > during migration. > > diff --git a/exec.c b/exec.c > index c9fa17d..9f7a4f7 100644 > --- a/exec.c > +++ b/exec.c > @@ -3438,6 +3438,7 @@ void cpu_physical_memory_rw(target_phys_addr_t addr, uint8_t *buf, > cpu_physical_memory_set_dirty_flags( > addr1, (0xff & ~CODE_DIRTY_FLAG)); > } > + xen_modified_memory(addr1, TARGET_PAGE_SIZE); > qemu_put_ram_ptr(ptr); > } > } else { This is pretty ugly. An alternative is to set up a periodic bitmap scan that looks at the qemu dirty bitmap and calls xen_modified_memory() for dirty page ranges, and clears the bitmap for the next pass. Is it workable? (is xen_modified_memory a hypercall, or does it maintain an in-memory structure?) -- error compiling committee.c: too many arguments to function