[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Memory Tracking API

From: Jaspal
Subject: Re: [Qemu-devel] Memory Tracking API
Date: Mon, 21 May 2012 08:58:58 +0530
User-agent: Mozilla/5.0 (X11; Linux i686; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

On 05/18/2012 12:17 AM, Richard W.M. Jones wrote:
On Thu, May 17, 2012 at 11:36:24PM +0530, Jaspal wrote:
Hi ,

Is it possible to keep a count of reads / writes taking place in a
vm using qemu ( using kvm as hypervisor ) ? Is there a api ( or any
patch ) for it ?
Memory reads and writes is surely going to generate a huge
amount of output!

There are various DEBUG_* symbols at the top of exec.c and ioport.c.
I've only used a few of these:

   DEBUG_UNASSIGNED - prints a message when an unmapped page is
       referenced (TCG only, presumably?)

   DEBUG_IOPORT - prints a message when any I/O port is referenced

   DEBUG_UNUSED_IOPORT - prints a message when a non-emulated I/O port
       is referenced

There are several more if you look at the code.


When are these functions called : kvm_read_guest_page , kvm_read_guest_atomic , kvm_write_guest_page present in kvm_main.c ? When qemu wants to read/write to a page ? If qemu has to read/write on the vm's memory ( RAM ) , does the process always involve kvm ?

Thanks ,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]