Ok, I succeeded in adding the process tracker hack into qemu and
linux, and also in keeping track of the memory access (thanks Yufei
Chen for the tip).
I also simulated a cycle counter by counting the number of
instructions executed, which is equivalent to a cpu with cpi equals to
1.
But, as I am s
On Tue, 27 Jul 2010, Jun Koi wrote:
> On Mon, Jul 26, 2010 at 8:16 PM, malc wrote:
> > On Mon, 26 Jul 2010, Eliot Moss wrote:
> >
> >> On 7/26/2010 6:20 AM, Llu?s wrote:
> >> > Eduardo Cruz writes:
[..snip..]
> >>
> >> In the context of another simulator, we developed a different
> >> technique,
On Mon, Jul 26, 2010 at 8:16 PM, malc wrote:
> On Mon, 26 Jul 2010, Eliot Moss wrote:
>
>> On 7/26/2010 6:20 AM, Llu?s wrote:
>> > Eduardo Cruz writes:
>> >
>> > > Thanks for your awnsers. Stean, after I find the right place to capture
>> > > the
>> > > reads and writes I'll definitely try your tr
> I define INSTR_MEM macro into a generation of a helper call, which will
> receive
> the run-time computed address.
Could you share how did you do this?
> If you'd also like to track pthreads and the like, you'll need some sort of
> backdoor communication channel.
Yes, I need to distinguish be
Eduardo Cruz writes:
> In the modification:
> Oh! BTW, my current prototype uses code like this on target-x86/translate.c:
>>
>> #define tcg_gen_qemu_ld8u(arg, addr, mem_index) \
>> do { \
>> INSTR_MEM(addr, 8);
In the modification:
Oh! BTW, my current prototype uses code like this on target-x86/translate.c:
>
> #define tcg_gen_qemu_ld8u(arg, addr, mem_index) \
> do { \
> INSTR_MEM(addr, 8); \
>
On Mon, Jul 26, 2010 at 6:20 PM, Lluís wrote:
> Eduardo Cruz writes:
>
>> Thanks for your awnsers. Stean, after I find the right place to capture the
>> reads and writes I'll definitely try your trace tool.
>
>> Until now, this is what i found:
>
>> I am using the x86-64 target, and I know that, f
malc writes:
>> > 2) instrumentation: a set of generic macros that signal events that might
>> > be
>> > of
>> > interest.
>>
>> Etc.
>>
>> In the context of another simulator, we developed a different
>> technique, which would be quite general and might be of interest
>> for QEMU. We comm
On Mon, 26 Jul 2010, Eliot Moss wrote:
> On 7/26/2010 6:20 AM, Llu?s wrote:
> > Eduardo Cruz writes:
> >
> > > Thanks for your awnsers. Stean, after I find the right place to capture
> > > the
> > > reads and writes I'll definitely try your trace tool.
> >
> > > Until now, this is what i found:
On 7/26/2010 6:20 AM, Lluís wrote:
Eduardo Cruz writes:
Thanks for your awnsers. Stean, after I find the right place to capture the
reads and writes I'll definitely try your trace tool.
Until now, this is what i found:
I am using the x86-64 target, and I know that, for instance, lots of r
Eduardo Cruz writes:
> Thanks for your awnsers. Stean, after I find the right place to capture the
> reads and writes I'll definitely try your trace tool.
> Until now, this is what i found:
> I am using the x86-64 target, and I know that, for instance, lots of reads
> pass here:
> target-i386/t
On Mon, Jul 26, 2010 at 6:21 AM, Eduardo Cruz wrote:
> Thanks for your awnsers. Stean, after I find the right place to capture the
> reads and writes I'll definitely try your trace tool.
> Until now, this is what i found:
>
> I am using the x86-64 target, and I know that, for instance, lots of rea
Thanks for your awnsers. Stean, after I find the right place to capture the
reads and writes I'll definitely try your trace tool.
Until now, this is what i found:
I am using the x86-64 target, and I know that, for instance, lots of reads
pass here:
target-i386/translate.c gen_op_ld_T1_A0()
Th
On Sat, Jul 24, 2010 at 3:17 AM, Yufei Chen wrote:
> On Fri, Jul 23, 2010 at 2:15 PM, Stefan Hajnoczi wrote:
>> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
>> wrote:
>>> Hi...
>>>
>>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz
>>> wrote:
Hello, I need qemu to keep track of all the m
On Fri, Jul 23, 2010 at 2:15 PM, Stefan Hajnoczi wrote:
> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
> wrote:
>> Hi...
>>
>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz
>> wrote:
>>> Hello, I need qemu to keep track of all the memory access made by the guest,
>>> including read, write and
On Fri, Jul 23, 2010 at 15:39, Stefan Hajnoczi wrote:
> The performance of these backends is different. If performance is a
> top concern, then the "ust" backend is probably the way to go. See
> http://lttng.org/ust for more info.
Oh wow, so let me put it another way: it's using LTTng? neat!
On Fri, Jul 23, 2010 at 8:34 AM, Jun Koi wrote:
> On Fri, Jul 23, 2010 at 3:15 PM, Stefan Hajnoczi wrote:
>> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
>> wrote:
>>> Hi...
>>>
>>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz
>>> wrote:
Hello, I need qemu to keep track of all the memo
On Fri, Jul 23, 2010 at 8:25 AM, Mulyadi Santosa
wrote:
> On Fri, Jul 23, 2010 at 13:15, Stefan Hajnoczi wrote:
>> Thanks Mulyadi, I think you are referring to the tracing work that
>> Prerna Saxena and I are doing. Here is the documentation:
>>
>> http://repo.or.cz/w/qemu/stefanha.git/blob/trac
On Fri, Jul 23, 2010 at 3:15 PM, Stefan Hajnoczi wrote:
> On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
> wrote:
>> Hi...
>>
>> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz
>> wrote:
>>> Hello, I need qemu to keep track of all the memory access made by the guest,
>>> including read, write and
On Fri, Jul 23, 2010 at 13:15, Stefan Hajnoczi wrote:
> Thanks Mulyadi, I think you are referring to the tracing work that
> Prerna Saxena and I are doing. Here is the documentation:
>
> http://repo.or.cz/w/qemu/stefanha.git/blob/tracing:/docs/tracing.txt
You're welcome Stefan :) I just hate to
On Fri, Jul 23, 2010 at 4:12 AM, Mulyadi Santosa
wrote:
> Hi...
>
> On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz wrote:
>> Hello, I need qemu to keep track of all the memory access made by the guest,
>> including read, write and the instruction fetches.
>
> AFAIK there are lots of experiments on t
Hi...
On Fri, Jul 23, 2010 at 05:30, Eduardo Cruz wrote:
> Hello, I need qemu to keep track of all the memory access made by the guest,
> including read, write and the instruction fetches.
AFAIK there are lots of experiments on this and has produces working
patches...at least from the posting of
Hello, I need qemu to keep track of all the memory access made by the guest,
including read, write and the instruction fetches.
I was using Simics to acomplish this task, but it is very slow.
I need the virtual address, the size of the operation, the cycle number when
it happened and if it is a rea
23 matches
Mail list logo
