1. Did you get the guest physical address for the load/store instructions?
No, I am getting the guest virtual address for the load and store
instructions.
2. The code you pasted seems translated code. The number of input code
could be smaller than this. So don't you think we should trap the
On Wed, Aug 15, 2012 at 4:57 AM, Prathmesh Kallurkar
prathmesh.kallur...@gmail.com wrote:
1. Did you get the guest physical address for the load/store instructions?
No, I am getting the guest virtual address for the load and store
instructions.
2. The code you pasted seems translated code.
Sorry friends for the misleading instructions in the previous mail.
cmp ecx, [r12+0x4]
mov r10b, [r13+0x0]
mov byte [rax+0xf], 0x0
mov byte [rax+rdx], 0x0
It seems all the above instructions are getting covered with the
tcg_gen_ld/st helpers.
But now I have stumbled upon another problem :
I
On Tue, Aug 14, 2012 at 11:58 AM, Prathmesh Kallurkar
prathmesh.kallur...@gmail.com wrote:
Sorry friends for the misleading instructions in the previous mail.
cmp ecx, [r12+0x4]
mov r10b, [r13+0x0]
mov byte [rax+0xf], 0x0
mov byte [rax+rdx], 0x0
It seems all the above instructions are
Hi, Prathmesh
I am working on getting the guest memory trace too. You said you have
trapped the guest memory access for most instructions. I have three
questions.
1. Did you get the guest physical address for the load/store instructions?
2. The code you pasted seems translated code. The number of
Hello friends,
I intend to use Qemu to generate a memory trace for the execution of a x86
guest operating system.
According to tcg
wikihttp://wiki.qemu.org/Documentation/TCG/backend-ops#Load.2FStorepage,
Qemu uses a handful of helpers to generate load/stores to the
target(guest) memory.
This list
