Re: [Qemu-devel] Which method executes the translated blocks (TBs)?

2014-07-10 Thread Anderson Sartor
iteration, the next TB will be executed, considering that chaining is disabled (1 TB per cpu_exec iteration). Am I missing something? Thanks 2014-07-09 10:52 GMT-03:00 Anderson Sartor : > Thank you for your response. > I want to count how many TBs that are executed. For this, I need to know &g

Re: [Qemu-devel] Which method executes the translated blocks (TBs)?

2014-07-10 Thread Anderson Sartor
mentioned. Thanks 2014-07-09 7:02 GMT-03:00 Peter Maydell : > On 8 July 2014 18:26, Anderson Sartor wrote: > > Hi all, > > Which method, in fact, executes the TBs (full-system emulation)? Is it > > tcg_qemu_tb_exec() from cpu_exec()? > > Yes. > > > At this point,

[Qemu-devel] Which method executes the translated blocks (TBs)?

2014-07-09 Thread Anderson Sartor
Hi all, Which method, in fact, executes the TBs (full-system emulation)? Is it tcg_qemu_tb_exec() from cpu_exec()? At this point, is it possible for the execution of the TB to be interrupted (it will try to execute this TB again)? If positive, how do I know whether a TB was completely executed? Th

[Qemu-devel] Dalvik execution on Android Emulator (QEMU)

2014-07-07 Thread Anderson Sartor
Hi all, I'm counting how many basic blocks are executed by a given application on the Android Emulator, so I modified QEMU to do this. However, I came across with the following: for 2 environment situations: (1) - only the emulator running in the host computer, (2) - the emulator + other processes

[Qemu-devel] Application PID on i386

2013-07-26 Thread Anderson Sartor
Hi all, I've been modyfing the QEMU source from Android SDK in order to trace a larger amount of data, I know this Android QEMU is already a modified version and it has additional code just for Android. However, if anyone have any idea how I can get the application PID for i386 architecture, I woul

Re: [Qemu-devel] QEMU option -d in_asm on i386

2013-07-15 Thread Anderson Sartor
Thank you for your answer. It was, as you guessed, the KVM acceleration, explicity calling "-disable-kvm" did the trick and everything is working now. Thanks again 2013/7/15 Peter Maydell > On 15 July 2013 13:21, Anderson Sartor wrote: > > Regarding the QEMU code pre

[Qemu-devel] QEMU option -d in_asm on i386

2013-07-15 Thread Anderson Sartor
Regarding the QEMU code present in the Android source (I tested on QEMU 1.1.2 as well and got the same results), I am able to get in_asm, out_asm, etc data with ARM and MIPS architectures. However on i386 nothing is saved to the log using any of the "-d" options. Why is i386 different? How can I ge