On Mon, Aug 27, 2012 at 8:15 PM, Steven wrote:
>> Guest code is accessed at the translation time by C functions and
>> I guess there are other layers of address translation caching. I wouldn't
>> try to interpret these _cmmu printouts and would instead instrument
>> [cpu_]ld{{u,s}{b,w},l,q}_code m
I added a special opcode, which is not used by existing x86. When the
process in the guest issues this opcode, the qemu starts to log its
mmu access.
On Mon, Aug 27, 2012 at 11:14 PM, 陳韋任 (Wei-Ren Chen)
wrote:
>> My final goal is to obtain the memory access trace for a particular
>> process in
> My final goal is to obtain the memory access trace for a particular
> process in the guest, so your patch really helps, except for too many
> kernel _mmu events.
How do you know guest is running which process, and log it's memory
access trace?
Regards,
chenwj
--
Wei-Ren Chen (陳韋任)
Computer
On Sat, Aug 25, 2012 at 4:41 PM, Max Filippov wrote:
> On Sat, Aug 25, 2012 at 9:20 PM, Steven wrote:
>> On Tue, Aug 21, 2012 at 3:18 AM, Max Filippov wrote:
>>> On Tue, Aug 21, 2012 at 9:40 AM, Steven wrote:
Hi, Max,
I wrote a small program to verify your patch could catch all the lo
On Sat, Aug 25, 2012 at 9:20 PM, Steven wrote:
> On Tue, Aug 21, 2012 at 3:18 AM, Max Filippov wrote:
>> On Tue, Aug 21, 2012 at 9:40 AM, Steven wrote:
>>> Hi, Max,
>>> I wrote a small program to verify your patch could catch all the load
>>> instructions from the guest. However, I found some pr
On Tue, Aug 21, 2012 at 9:40 AM, Steven wrote:
> Hi, Max,
> I wrote a small program to verify your patch could catch all the load
> instructions from the guest. However, I found some problem from the
> results.
>
> The guest OS and the emulated machine are both 32bit x86. My simple
> program in th
Hi, Max,
I wrote a small program to verify your patch could catch all the load
instructions from the guest. However, I found some problem from the
results.
The guest OS and the emulated machine are both 32bit x86. My simple
program in the guest declares an 1048576-element integer array,
initialize
On Fri, Aug 17, 2012 at 03:57:55PM +0400, Max Filippov wrote:
> On Fri, Aug 17, 2012 at 3:14 PM, 陳韋任 (Wei-Ren Chen)
> wrote:
> >> > On Thu, Aug 16, 2012 at 7:49 PM, Steven wrote:
> >> > [...]
> >> >> I want to get the guest memory address in the instruction mov
> >> >> 0x4(%ebx) %eax, whic is 0x
On Fri, Aug 17, 2012 at 3:14 PM, 陳韋任 (Wei-Ren Chen)
wrote:
>> > On Thu, Aug 16, 2012 at 7:49 PM, Steven wrote:
>> > [...]
>> >> I want to get the guest memory address in the instruction mov
>> >> 0x4(%ebx) %eax, whic is 0x4(%ebx).
>> >> Since %ebx is not resolved until the execution time, the co
> > On Thu, Aug 16, 2012 at 7:49 PM, Steven wrote:
> > [...]
> >> I want to get the guest memory address in the instruction mov
> >> 0x4(%ebx) %eax, whic is 0x4(%ebx).
> >> Since %ebx is not resolved until the execution time, the code in
> >> softmmu_header.h does not generate any hit or miss inf
> To verify what is translation time and what is the run time, I log the
> register information before disassembling each guest code. I copied
> some results from the log file, which is generated at run time of a
> guest machine.
>
> EAX= EBX=6ffc
> IN:
> 0x
On Fri, Aug 17, 2012 at 9:38 AM, Steven wrote:
> Hi, Max,
> I appreciate your help and got some results using your patch. But I
> still have two questions as blow.
>
>>> I see that with the following patch
>>>
>>> diff --git a/softmmu_template.h b/softmmu_template.h
>>> index b8bd700..2d02133 1006
Hi, Max,
I appreciate your help and got some results using your patch. But I
still have two questions as blow.
>> I see that with the following patch
>>
>> diff --git a/softmmu_template.h b/softmmu_template.h
>> index b8bd700..2d02133 100644
>> --- a/softmmu_template.h
>> +++ b/softmmu_template.h
On Thu, Aug 16, 2012 at 10:31 PM, Max Filippov wrote:
> On Thu, Aug 16, 2012 at 9:49 PM, Steven wrote:
>> On Thu, Aug 16, 2012 at 1:43 PM, Max Filippov wrote:
>>> On Thu, Aug 16, 2012 at 9:37 PM, Max Filippov wrote:
On Thu, Aug 16, 2012 at 9:29 PM, Steven wrote:
> On Thu, Aug 16, 2012
On Thu, Aug 16, 2012 at 2:51 PM, Laurent Desnogues
wrote:
> On Thu, Aug 16, 2012 at 7:49 PM, Steven wrote:
> [...]
>> I want to get the guest memory address in the instruction mov
>> 0x4(%ebx) %eax, whic is 0x4(%ebx).
>> Since %ebx is not resolved until the execution time, the code in
>> softmmu
On Thu, Aug 16, 2012 at 12:54 PM, Peter Maydell
wrote:
> On 16 August 2012 17:36, Steven wrote:
>> I would like to get a trace of guest memory access. So I can not use
>> "info registers".
>> What I want to do is that when tcg fetches a load instruction at
>> disas_insns(), the guest memory addre
On Thu, Aug 16, 2012 at 7:49 PM, Steven wrote:
[...]
> I want to get the guest memory address in the instruction mov
> 0x4(%ebx) %eax, whic is 0x4(%ebx).
> Since %ebx is not resolved until the execution time, the code in
> softmmu_header.h does not generate any hit or miss information.
> Do you k
On Thu, Aug 16, 2012 at 9:49 PM, Steven wrote:
> On Thu, Aug 16, 2012 at 1:43 PM, Max Filippov wrote:
>> On Thu, Aug 16, 2012 at 9:37 PM, Max Filippov wrote:
>>> On Thu, Aug 16, 2012 at 9:29 PM, Steven wrote:
On Thu, Aug 16, 2012 at 1:00 PM, Max Filippov wrote:
> On Thu, Aug 16, 2012
On Thu, Aug 16, 2012 at 9:37 PM, Max Filippov wrote:
> On Thu, Aug 16, 2012 at 9:29 PM, Steven wrote:
>> On Thu, Aug 16, 2012 at 1:00 PM, Max Filippov wrote:
>>> On Thu, Aug 16, 2012 at 8:36 PM, Steven wrote:
On Thu, Aug 16, 2012 at 4:02 AM, 陳韋任 (Wei-Ren Chen)
wrote:
>> I would l
On Thu, Aug 16, 2012 at 1:43 PM, Max Filippov wrote:
> On Thu, Aug 16, 2012 at 9:37 PM, Max Filippov wrote:
>> On Thu, Aug 16, 2012 at 9:29 PM, Steven wrote:
>>> On Thu, Aug 16, 2012 at 1:00 PM, Max Filippov wrote:
On Thu, Aug 16, 2012 at 8:36 PM, Steven wrote:
> On Thu, Aug 16, 2012
On Thu, Aug 16, 2012 at 9:29 PM, Steven wrote:
> On Thu, Aug 16, 2012 at 1:00 PM, Max Filippov wrote:
>> On Thu, Aug 16, 2012 at 8:36 PM, Steven wrote:
>>> On Thu, Aug 16, 2012 at 4:02 AM, 陳韋任 (Wei-Ren Chen)
>>> wrote:
> I would like to is there any function that could log the register
On Thu, Aug 16, 2012 at 1:00 PM, Max Filippov wrote:
> On Thu, Aug 16, 2012 at 8:36 PM, Steven wrote:
>> On Thu, Aug 16, 2012 at 4:02 AM, 陳韋任 (Wei-Ren Chen)
>> wrote:
I would like to is there any function that could log the register
content of the guest machine, like "info registers" i
On Thu, Aug 16, 2012 at 1:15 PM, Peter Maydell wrote:
> On 16 August 2012 18:13, Steven wrote:
>> So the run time function should be tcg_out_qemu_ld, right?
>
> No, tcg_out_qemu_ld is a translate time function, which emits
> the native (x86 in this case) instructions necessary to perform
> a gues
On 16 August 2012 18:13, Steven wrote:
> So the run time function should be tcg_out_qemu_ld, right?
No, tcg_out_qemu_ld is a translate time function, which emits
the native (x86 in this case) instructions necessary to perform
a guest load.
-- PMM
On Thu, Aug 16, 2012 at 12:54 PM, Peter Maydell
wrote:
> On 16 August 2012 17:36, Steven wrote:
>> I would like to get a trace of guest memory access. So I can not use
>> "info registers".
>> What I want to do is that when tcg fetches a load instruction at
>> disas_insns(), the guest memory addre
On Thu, Aug 16, 2012 at 8:36 PM, Steven wrote:
> On Thu, Aug 16, 2012 at 4:02 AM, 陳韋任 (Wei-Ren Chen)
> wrote:
>>> I would like to is there any function that could log the register
>>> content of the guest machine, like "info registers" in the qemu
>>> monitor mode.
>>
>> Why not check how "info
On 16 August 2012 17:36, Steven wrote:
> I would like to get a trace of guest memory access. So I can not use
> "info registers".
> What I want to do is that when tcg fetches a load instruction at
> disas_insns(), the guest memory address should be calculated.
You cannot calculate the guest memor
On Thu, Aug 16, 2012 at 4:02 AM, 陳韋任 (Wei-Ren Chen)
wrote:
>> I would like to is there any function that could log the register
>> content of the guest machine, like "info registers" in the qemu
>> monitor mode.
>
> Why not check how "info registes" be implemented in QEMU? ;)
> I guess you just
> I would like to is there any function that could log the register
> content of the guest machine, like "info registers" in the qemu
> monitor mode.
Why not check how "info registes" be implemented in QEMU? ;)
I guess you just have to log env->regs or something like that.
Regards,
chenwj
--
Hi,
I would like to is there any function that could log the register
content of the guest machine, like "info registers" in the qemu
monitor mode.
Thanks.
steven
30 matches
Mail list logo
