From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Checking guest memory pages changes from host userspace Date: Sun, 21 Jun 2009 18:51:34 +0300 Message-ID: <4A3E5706.9070408@redhat.com> References: <18C018878FB0244EB71B7FE328978A32679FD52B@rrsmsx503.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" To: "Passera, Pablo R" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:49772 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751459AbZFUPut (ORCPT ); Sun, 21 Jun 2009 11:50:49 -0400 In-Reply-To: <18C018878FB0244EB71B7FE328978A32679FD52B@rrsmsx503.amr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/19/2009 09:09 PM, Passera, Pablo R wrote: > Hi list, > I need to monitor some guest memory pages. I need to know if the information in these pages was changed. For this, I was thinking to mark the guest memory pages in some way (like write protecting them) so a page fault is generated. Then manage this fault inside qemu. Is there some API in libkvm that allows me to do this? > You can use the dirty memory logging API. vga uses this to track which regions of the screen have changed, and live migration uses it to allow the guest to proceed while copying its memory to the other node. It works exactly by write protecting guest memory and trapping the resultant fault. -- error compiling committee.c: too many arguments to function