diff options
author | jkoshy <jkoshy@FreeBSD.org> | 2008-11-27 09:00:47 +0000 |
---|---|---|
committer | jkoshy <jkoshy@FreeBSD.org> | 2008-11-27 09:00:47 +0000 |
commit | aa86a7c59edb19ee67bcf28d9465dc88c0b1fd6a (patch) | |
tree | b416bbd4293b5dc3b86cfd87f09039063e60517b /LOCKS | |
parent | 272e95193bef3d1cacf8bf5d82b6f7bbe6d500a7 (diff) | |
download | FreeBSD-src-aa86a7c59edb19ee67bcf28d9465dc88c0b1fd6a.zip FreeBSD-src-aa86a7c59edb19ee67bcf28d9465dc88c0b1fd6a.tar.gz |
- Add support for PMCs in Intel CPUs of Family 6, model 0xE (Core Solo
and Core Duo), models 0xF (Core2), model 0x17 (Core2Extreme) and
model 0x1C (Atom).
In these CPUs, the actual numbers, kinds and widths of PMCs present
need to queried at run time. Support for specific "architectural"
events also needs to be queried at run time.
Model 0xE CPUs support programmable PMCs, subsequent CPUs
additionally support "fixed-function" counters.
- Use event names that are close to vendor documentation, taking in
account that:
- events with identical semantics on two or more CPUs in this family
can have differing names in vendor documentation,
- identical vendor event names may map to differing events across
CPUs,
- each type of CPU supports a different subset of measurable
events.
Fixed-function and programmable counters both use the same vendor
names for events. The use of a class name prefix ("iaf-" or
"iap-" respectively) permits these to be distinguished.
- In libpmc, refactor pmc_name_of_event() into a public interface
and an internal helper function, for use by log handling code.
- Minor code tweaks: staticize a global, freshen a few comments.
Tested by: gnn
Diffstat (limited to 'LOCKS')
0 files changed, 0 insertions, 0 deletions