Re: [perf-discuss] An idea to enhance cpc

[Jin Yao]

> Hi Jin Yao
> 
> 1. Regarding your RMA example, wouldn't you be able
> to use the dtrace 
> cpc provider to get this information?
> 
> 2. How do you propose handling the case where both
> the proposed 
> per-hardware thread data and overflow profiling are
> enabled?
> 
> Thanks
> /kuriakose
> _______________________________________________
> perf-discuss mailing list
> perf-discuss@opensolaris.org
> 

Thanks kuriakose's suggestions.

I just tried the dtrace cpc provider to check if it can satisfy my 
requirements. 
I wrote a dtrace script and test it on nhm-ep.

#!/usr/sbin/dtrace -s

cpc:::mem_load_retired.llc_miss-all-5000
{
        @llc_miss[pid,tid,cpu] = count();
}

cpc:::mem_uncore_retired.remote_dram-all-5000
{
        @rma[pid,tid,cpu] = count();
}

cpc:::mem_uncore_retired.local_dram-all-5000
{
        @lma[pid,tid,cpu] = count();
}

cpc:::instr_retired.any-all-1000000
{
        @ir[pid,tid,cpu] = count();
}

cpc:::cpu_clk_unhalted.thread-all-1000000
{
        @clk[pid,tid,cpu] = count();
}

END
{
        printf("\nllc_miss");
        printa(@llc_miss);
        printf("\nrma");
        printa(@rma);
        printf("\nlma");
        printa(@lma);
        printf("\nir");
        printa(@ir);
        printf("\nclk");
        printa(@clk);
}

The script does work and most of output are the information I need, but only 
without the output of "clk". Do I lost something special in above script?
Or do I need to manually assign "cpu_clk_unhalted.thread" to a special pic?

But in a word, the dtrace cpc provider can successfully give me the information
which my patch want to provide. 

Thanks
Jin Yao
-- 
This message posted from opensolaris.org
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org