Hi, Corey

  Thanks. It is really help. :)

> are not in the list given by "perf list", you must use a raw event code, 
> by specifying an 'r' followed by the event's hex code.

  I note there is a line at the bottom of `perf list` says,

rNNN (see 'perf list --help' on how to encode it) [Raw hardware event 
descriptor]

  I think this is what you called "raw event code", right?
 
> Some of those raw event codes are going to be the same as the events 
> used internally by the kernel for the "generic hardware events", but the 
> only way to find out which specific hardware events are used for which 
> "generic hardware events", you'd have to read the kernel code.  There is 
> no translation available in user space, via perf or any other tool. 
> When perf was designed, it was believed that most users do not need this 
> mapping information, so there is no API provided to obtain it.

  From Documentation/perf-list.txt, I can only guess on x86 for example,
I have to see "Intel® 64 and IA-32 Architectures Software Developer's
Manual" to find out event name as an input to `evt2raw`. But some are
success, some are failed. Is there a better way to find out what event
string can be used?

  Thanks.

Regards,
chenwj

-- 
Wei-Ren Chen (陳韋任)
Parallel Processing Lab, Institute of Information Science,
Academia Sinica, Taiwan (R.O.C.)
Tel:886-2-2788-3799 #1667

------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
perfmon2-devel mailing list
perfmon2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/perfmon2-devel

Reply via email to