[perfmon2] MEM_UOPS_RETIRED event on Ivy Bridge

Hi, I am facing a problem in counting MEM_UOPS_RETIRED event on Ivy Bridge. I am trying to use it with the *task* command and I get following error: $> task -i -e MEM_UOPS_RETIRED:ALL_LOADS ls task: cannot attach event0 MEM_UOPS_RETIRED:ALL_LOADS: Invalid argument. I am facing similar problem fo

Re: [perfmon2] MEM_UOPS_RETIRED event on Ivy Bridge

On Thu, Sep 4, 2014 at 12:34 PM, Bhavishya Goel wrote: > Hi, > > I am facing a problem in counting MEM_UOPS_RETIRED event on Ivy Bridge. I > am trying to use it with the *task* command and I get following error: > > $> task -i -e MEM_UOPS_RETIRED:ALL_LOADS ls > task: cannot attach event0 MEM_UOPS

Re: [perfmon2] MEM_UOPS_RETIRED event on Ivy Bridge

Thanks Stephane. Yes, it would be very helpful if you can guide me how to apply the workaround. On Thu, Sep 4, 2014 at 4:44 PM, Stephane Eranian wrote: > > > > On Thu, Sep 4, 2014 at 12:34 PM, Bhavishya Goel > wrote: > >> Hi, >> >> I am facing a problem in counting MEM_UOPS_RETIRED event on Iv

Re: [perfmon2] Error reporting when using invalid combination of umasks.

> > > When I added a modified version of check_scheduability() to the uncore > > component it now detects that the two events with constraint conflicts > > cannot be used together. This allows PAPI to return an error at add > > event time which is better than reporting it when trying to read the