Yes, it worked. I guess I had wrongly interpreted how task works. Shouldn't
it only count the events from the passed binary and it's child processes
(if inheritance flag is turned on)?
On Tue, Sep 23, 2014 at 9:26 PM, Stephane Eranian
wrote:
> On Tue, Sep 23, 2014 at 8:58 PM, Bhavishya Goel
> w
On Tue, Sep 23, 2014 at 8:58 PM, Bhavishya Goel
wrote:
> Hi Vince,
>
> I am using lipfm4 directly. This is the command line I use:
>
> task -i -e MEM_UOPS_RETIRED:ALL_LOADS,MEM_UOPS_RETIRED:ALL_STORES ./loop.
task -i -e MEM_UOPS_RETIRED:ALL_LOADS:u,MEM_UOPS_RETIRED:ALL_STORES:u ./loop.
See if th
Hi Vince,
I am using lipfm4 directly. This is the command line I use:
task -i -e MEM_UOPS_RETIRED:ALL_LOADS,MEM_UOPS_RETIRED:ALL_STORES ./loop.
>From what I understand, the task example in libpfm4 doesn't count kernel
level events.
Regards
Bhavi
On Tue, Sep 23, 2014 at 8:24 PM, Vince Weaver
w
On Tue, 23 Sep 2014, Bhavishya Goel wrote:
> When I use Vtune to verify these values, it counts 0 loads and stores for
> this loop as expected.
you need to specify you only want userspace measurements.
By default you are probably getting kernel values included too.
You don't give your meth
When I use Vtune to verify these values, it counts 0 loads and stores for
this loop as expected.
On Tue, Sep 23, 2014 at 7:06 PM, Bhavishya Goel
wrote:
> Hi,
>
> I am using the task example to count loads and stores for my application,
> which mainly constitutes of a loop doing some integer addi
