Pete Stevenson writes:
> Hi All -
> I would like to generate a trace of all memory accesses (i.e. read or write,
> physical address, and data content/payload). The end goal is to use this trace
> to drive a separate memory system simulator. Ideally, the trace would also
> provide core-id and a tim
On Fri, Apr 18, 2014 at 12:48 PM, Pavel Dovgaluk
wrote:
> You can insert tracing code into the functions from the
> “include\exec\softmmu_template.h” file: like helper_le_ld_name,
> helper_le_st_name and so on.
It's not enough, you also need to disable memory access fast path so that
these functi
other functions and files.
Pavel Dovgaluk
From: qemu-devel-bounces+pavel.dovgaluk=ispras...@nongnu.org
[mailto:qemu-devel-bounces+pavel.dovgaluk=ispras...@nongnu.org] On Behalf Of
Pete Stevenson
Sent: Friday, April 18, 2014 3:31 AM
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] memory access
Hi All -
I would like to generate a trace of all memory accesses (i.e. read or
write, physical address, and data content/payload). The end goal is to use
this trace to drive a separate memory system simulator. Ideally, the trace
would also provide core-id and a timestamp (but I am not as optimis