From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from [140.186.70.92] (port=44243 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OcDr3-0001kF-Pk
	for qemu-devel@nongnu.org; Fri, 23 Jul 2010 04:43:43 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <stefanha@gmail.com>) id 1OcDr1-0007dl-0J
	for qemu-devel@nongnu.org; Fri, 23 Jul 2010 04:43:41 -0400
Received: from mail-vw0-f45.google.com ([209.85.212.45]:42579)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <stefanha@gmail.com>) id 1OcDr0-0007dT-J2
	for qemu-devel@nongnu.org; Fri, 23 Jul 2010 04:43:38 -0400
Received: by vws19 with SMTP id 19so1344219vws.4
	for <qemu-devel@nongnu.org>; Fri, 23 Jul 2010 01:43:36 -0700 (PDT)
MIME-Version: 1.0
In-Reply-To: <AANLkTikNVZdYTaLC15f7WDOQSYy1eU7P8DA4RjzgzxDq@mail.gmail.com>
References: <AANLkTinMquF1oXgDg5fyKNF1Rxcz2_vMSvJmyH7E46bi@mail.gmail.com>
	<AANLkTimyuF6ZNaWXar2qYwC_tl4pclCu136dH8wpa9xM@mail.gmail.com>
	<AANLkTili9UdnzkpKh-YBhARzI-1NWewuvf1b3pH-5Zd9@mail.gmail.com>
	<AANLkTikNVZdYTaLC15f7WDOQSYy1eU7P8DA4RjzgzxDq@mail.gmail.com>
Date: Fri, 23 Jul 2010 09:43:36 +0100
Message-ID: <AANLkTim+JBSgSRUyH8xPkLnBJ+_omgOVf7XyO9-_gOve@mail.gmail.com>
Subject: Re: [Qemu-devel] memory trace with qemu
From: Stefan Hajnoczi <stefanha@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Jun Koi <junkoi2004@gmail.com>
Cc: qemu-devel@nongnu.org, Prerna Saxena <prerna@linux.vnet.ibm.com>

On Fri, Jul 23, 2010 at 8:34 AM, Jun Koi <junkoi2004@gmail.com> wrote:
> On Fri, Jul 23, 2010 at 3:15 PM, Stefan Hajnoczi <stefanha@gmail.com> wro=
te:
>> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
>> <mulyadi.santosa@gmail.com> wrote:
>>> Hi...
>>>
>>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz <eduardohmdacruz@gmail.com>=
 wrote:
>>>> Hello, I need qemu to keep track of all the memory access made by the =
guest,
>>>> including read, write and the instruction fetches.
>>>
>>> AFAIK there are lots of experiments on this and has produces working
>>> patches...at least from the posting of the creator. There is even a
>>> patch floating to start creating trace framework a while ago.
>>
>> Thanks Mulyadi, I think you are referring to the tracing work that
>> Prerna Saxena and I are doing. =A0Here is the documentation:
>>
>> http://repo.or.cz/w/qemu/stefanha.git/blob/tracing:/docs/tracing.txt
>>
>> The patches apply to qemu.git. =A0You can define trace events in the
>> trace-events file and then call them from places in the code. =A0There
>> is a script to pretty-print the binary trace file that QEMU produces.
>>
>
> what trace events do you support now?

The existing set of trace events is here:

http://repo.or.cz/w/qemu/stefanha.git/blob/tracing:/trace-events

It is a limited set of pre-defined trace events - most come from my
block latency tracing work.  But adding trace events is easy.

There is a task on the roadmap to get broader tracing coverage before
submitting the patches to qemu.git.  If you add trace events that you
feel would be useful to others, please don't hesitate to send patches
so they can be included.

Stefan

> thanks,
> J
>