Stephane -
I imported the latest sources from libpfm the other day in preparation for
the PAPI-C release. Today our regression tests showed 0 counts for
PAPI_FP_OPS. In tracing this problem we discovered that the latest
intel_corei7_events.h has a whole bunch of new PFMLIB_NHM_UMASK_NCOMBO flags
set, including on FP_COMP_OPS_EXE. I don't know about the other instances,
but I know that UMASKS can be combined for that event. Our definition of
PAPI_FP_OPS is:
FP_COMP_OPS_EXE:SSE_DOUBLE_PRECISION:SSE_SINGLE_PRECISION
This produces 0 counts.
If we clear that flag, we get the proper # of counts.
If we use: FP_COMP_OPS_EXE:SSE_DOUBLE_PRECISION we get the right answer;
If we use: FP_COMP_OPS_EXE:SSE_SINGLE_PRECISION we get 0.
I hesitate to change just this one flag without knowing the reasoning behind
all these restrictions. But I can't release PAPI if it doesn't count
floating point. The other concern is that even though we passed in two
UMASKs to an event that supposedly could only handle one, we didn't see an
error message. Is that PAPI's fault or libpfm's?
Thanks,
- dan
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel
