On Sat, Jul 24, 2010 at 3:17 AM, Yufei Chen <address@hidden
> On Fri, Jul 23, 2010 at 2:15 PM, Stefan Hajnoczi <address@hidden
>> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
>>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz <address@hidden
>>>> Hello, I need qemu to keep track of all the memory access made by the guest,
>>>> including read, write and the instruction fetches.
> I don't think Qemu can provide cycle number information. But other
> information are all available.
>>> 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. Here is the documentation:
>> The patches apply to qemu.git. You can define trace events in the
>> trace-events file and then call them from places in the code. There
>> is a script to pretty-print the binary trace file that QEMU produces.
>> Eduardo, if you think this might be what you're looking for, please
>> give it a try. I am on #qemu and #kvm IRC if you need any help. Any
>> feedback will be valuable to us as we prepare these patches for
>> submission to qemu.git.
>> I believe the tracing framework answers the "Any ideas of how I can
>> record these information with qemu?" part of your question :). I
>> don't have experience in the TCG, so I can't give advice on how to
>> best get at the memory accesses, but I hope this helps you one step
> Can this framework trace memory access event? I guess this would be
> more difficult to do in KVM than in TCG.