Thanks. In fact, I don't need QEMU to have realized this kind of trace about instructions and therefore this is my ToDoList on QEMU.
Now I have made some progress and still have some problems. So far, I have found that in the source code of QEMU(qemu-2.7.0-rc5-5/tcg/tcg-opc.h) there are a lot of instructions type, such as load/store, arith, shift/rotetes and so on. All I am confused about is where to identify the type of instruction, such as Load/Store/Move instructions and count them for a specified benchmark. Best 2017-11-01 19:40 GMT+08:00 Peter Maydell <peter.mayd...@linaro.org>: > On 1 November 2017 at 02:35, 李阳 <liyang.cs....@gmail.com> wrote: > > Recently, I want to use QEMU to trace the instruction features of the > > specified binary. > > > > My host: X86 > > Guest: ARMv8, > > > > I run the benchmark on the AArch64 Operating System in QEMU and I want to > > collect the instruction data of the binary. > > The instruction features include: # of INT ALU, #of INT MUL, # of INT > DIV, > > # of FP ADD, # of FP MUL, # of FP DIV, # of LOAD, # of STORE. > > > > I have no idea about where and how to identify the type of instruction. > > QEMU does not currently provide any mechanism for doing this > kind of tracing, I'm afraid. (There's some experimental > stuff floating around but using it requires some familiarity > with QEMU internals.) You may be able to get what you want > by taking debug traces with -d options and post-processing > them, but that's not trivial and you need to know what the > debug logs are telling you to interpret them correctly. > > We're looking at adding a proper tracing/instrumentation > feature, but that's still in the design proposals stage. > > thanks > -- PMM >
