summaryrefslogtreecommitdiffstats
path: root/Documentation/zh_CN
diff options
context:
space:
mode:
authorMark Rutland <mark.rutland@arm.com>2011-05-17 11:20:11 +0100
committerWill Deacon <will.deacon@arm.com>2011-08-31 10:50:12 +0100
commit8be3f9a2385f91f7bf5c58f351e24b9247898e8f (patch)
tree5e293c7702f36b7eafd611bd5e8e710719643ac4 /Documentation/zh_CN
parent3fc2c83087717dc88003428245d97b9d432fff2d (diff)
downloadop-kernel-dev-8be3f9a2385f91f7bf5c58f351e24b9247898e8f.zip
op-kernel-dev-8be3f9a2385f91f7bf5c58f351e24b9247898e8f.tar.gz
ARM: perf: remove cpu-related misnomers
Currently struct cpu_hw_events stores data on events running on a PMU associated with a CPU. As this data is general enough to be used for system PMUs, this name is a misnomer, and may cause confusion when it is used for system PMUs. Additionally, 'armpmu' is commonly used as a parameter name for an instance of struct arm_pmu. The name is also used for a global instance which represents the CPU's PMU. As cpu_hw_events is now not tied to CPU PMUs, it is renamed to pmu_hw_events, with instances of it renamed similarly. As the global 'armpmu' is CPU-specfic, it is renamed to cpu_pmu. This should make it clearer which code is generic, and which is coupled with the CPU. Signed-off-by: Mark Rutland <mark.rutland@arm.com> Reviewed-by: Will Deacon <will.deacon@arm.com> Reviewed-by: Jamie Iles <jamie@jamieiles.com> Reviewed-by: Ashwin Chaugule <ashwinc@codeaurora.org> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'Documentation/zh_CN')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud