are performance
counters.
Vince
De: Vince Weaver
Para: Boris Cámara
Cc: qemu-devel@nongnu.org
Enviadas: Segunda-feira, 5 de Abril de 2010 22:41:52
Assunto: Re: [Qemu-devel] full dynamic instruction trace for MIPS target
> I think the correct way to get the full instruction trace on a MIPS
&
ámara
Cc: qemu-devel@nongnu.org
Enviadas: Segunda-feira, 5 de Abril de 2010 22:41:52
Assunto: Re: [Qemu-devel] full dynamic instruction trace for MIPS target
> I think the correct way to get the full instruction trace on a MIPS
> emulated processor is:
the way you describe is slow be
] ?
I didnt run your patch yet so I m not sure that I said is 100% correct. :)
De: Vince Weaver
Para: Boris Cámara
Cc: qemu-devel@nongnu.org
Enviadas: Segunda-feira, 5 de Abril de 2010 22:41:52
Assunto: Re: [Qemu-devel] full dynamic instruction trace for MIPS
> I think the correct way to get the full instruction trace on a MIPS
> emulated processor is:
the way you describe is slow because you are constantly re-generating the
TBs. The best way to do this is to add your instrumentation to the TBs.
I have code that does that for a recent version of Q
s?
thanks,
De: Richard Henderson
Para: Boris Cámara
Cc: qemu-devel@nongnu.org
Enviadas: Segunda-feira, 5 de Abril de 2010 19:41:52
Assunto: Re: [Qemu-devel] full dynamic instruction trace for MIPS target
On 04/05/2010 03:09 PM, Boris Cámara wrote:
> I think th
On 04/05/2010 03:09 PM, Boris Cámara wrote:
> I think the correct way to get the full instruction trace on a MIPS
> emulated processor is:
-singlestep -d exec
That gives you the address of each instruction executed.
I'm not sure what else you want than this, as you havn't said.
r~
Hi,
I think the correct way to get the full instruction trace on a MIPS emulated
processor is:
-Disabling the tb cache: I did this by modifying the tb_find_slow() and
tb_find_fast() functions to ever go to "not_found" label where the code is
translated with no cache searches.
-Loggin th