[Gems-users] Profiling memory access with Opal


Date: Sun, 21 Jan 2007 23:30:21 -0500
From: Wei Chen <weichen@xxxxxxxxxxxxxx>
Subject: [Gems-users] Profiling memory access with Opal
Hi,

I'm collecting a trace of memory accesses for a benchmark. Everything
is going well when only loading ruby module. I did the profiling in
this way:
changing related protocol file, i.e. MOESI_CMP_token_L2cache.sm to add
address information, also some code of RubySlicc_profiler.sm
RubySlicc_profiler_interface.h is changed. Then, under
/ruby/profiler/Profiler.c, I instrument addL2StatSample to output the
physical address, e.g
cout<<"Address is "<<address.getAddress()<<endl; //address is the added
argument.

When I load ruby, the output is like
Address is 4231424
Address is 4231488
Address is 8821696
Address is 217048064
......

But when Opal is loaded, I cannot see any of these profiling
information. Can anyone tell me why and how to fix my problem? Thx.

-Wei
[← Prev in Thread] Current Thread [Next in Thread→]
  • [Gems-users] Profiling memory access with Opal, Wei Chen <=