On Mon, Oct 24, 2011 at 06:55:59PM +0800, Deng-Cheng Zhu wrote: > Update the raw event info for 74K according to the latest document. > +/* > + * MIPS document MD00519 (MIPS32(r) 74K(tm) Processor Core Family Software > + * User's Manual, Revision 01.05) > + */ > #define IS_UNSUPPORTED_74K_EVENT(r, b) \ > - ((r) == 5 || ((r) >= 135 && (r) <= 137) || \ > - ((b) >= 10 && (b) <= 12) || (b) == 22 || (b) == 27 || \ > - (b) == 33 || (b) == 34 || ((b) >= 47 && (b) <= 49) || \ > - (r) == 178 || (b) == 55 || (b) == 57 || (b) == 60 || \ > - (b) == 61 || (r) == 62 || (r) == 191 || \ > - ((b) >= 64 && (b) <= 127)) > + ((r) == 5 || (r) == 135 || ((b) >= 10 && (b) <= 12) || \ > + (b) == 27 || (b) == 33 || (b) == 34 || (b) == 47 || \ > + (b) == 48 || (r) == 178 || (r) == 187 || (b) == 60 || \ > + (b) == 61 || (r) == 191 || (r) == 71 || (r) == 72 || \ > + (b) == 73 || ((b) >= 77 && (b) <= 127)) I wonder if such detailed checking of the performance counter event numbers is really needed? As long as feeding an bad number only results in undefined counts of the performance counters I think we may be better of by not checking the event numbers in detail. Afair there are MIPS licensee who have modified the counters to count extra events so I sense some madness in that direction. Ralf