Hi Wei-Ren,
Thanks for your reply.
According your email, the function "do_interrupt" handle the external
interrupt just like keyboard interrupt, and the function "gen_exception"
handle the exception just like “SWI”.etc. So the function “gen_exception”
seems to be the answer.
Any comments are app
> Now I have some probem with the exception handle. I found the funciton
> "do_interrupt" in "target-arm/helper.c" and "gen_exception" in
> "target-arm/translate.c" seems to handle the exceptions. But I am comfused
> with those two functions, which function will do the really work about
> generatin
Hi Chenwj,
Thanks for your kindly help. Would you mind give me more help?
Now I have some probem with the exception handle. I found the funciton
"do_interrupt" in "target-arm/helper.c" and "gen_exception" in
"target-arm/translate.c" seems to handle the exceptions. But I am comfused
with those two
> Now I want to moniter memory access on QEMU (guest virtual or guest
> physical).
> I found that QEMU will translate arm instructions into TCG instructions,
> and the TCG instructions will be translated into X86 instructions.
>
> The function "tcg_out_op"(tcg/i386/tcg_target.c) will translate the
Dear All,
Now I want to moniter memory access on QEMU (guest virtual or guest
physical).
I found that QEMU will translate arm instructions into TCG instructions,
and the TCG instructions will be translated into X86 instructions.
The function "tcg_out_op"(tcg/i386/tcg_target.c) will translate the
