summaryrefslogtreecommitdiff
path: root/tools/lib/find_bit.c
diff options
context:
space:
mode:
authorHeiko Carstens <hca@linux.ibm.com>2025-11-14 11:30:50 +0100
committerHeiko Carstens <hca@linux.ibm.com>2025-11-14 11:30:50 +0100
commitf518d469fe59e1b3b9b0b4d845926e07153924fd (patch)
tree8c0ad103dad347bb24d2564634016fb1d675a9ce /tools/lib/find_bit.c
parentc1287d67c3a91aa19e4d9bbd3ad943cfbfa6bed4 (diff)
parent492578d3a2bce24b73f24728bc244add0bdf3fee (diff)
Merge branch 'pai-pmu-merge'
Thomas Richter says: ==================== The PAI PMUs pai_crypto and pai_ext both operate on memory mapped counters supported by z16 and follow on machines. These memory mapped counters have a lot in common, like: - validation, installing and removing events - starting and stopping events - retrieving counter values - collecting sample data. However both PMU drivers have slightly different parameters, for example: - different mapped memory size - different number of supported counters - different counter numbers and names - different bits in the CR0 register - different anchor address in lowcore Due to these different parameters, two independent PMUs have been developed. However both PMU drivers have very much in common and most of the PMU call back functions look very similar and are sometimes identical. This patch set combines both independent PMU device drivers perf_pai_crypto.c and per_pai_ext.c into one device driver. The new device driver operations on a table which contains the different parameters and uses common functions for event operations. Result is one PAI PMU driver which supports both PMUs. It is also extendable to support new PAI PMUs. ==================== Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'tools/lib/find_bit.c')
0 files changed, 0 insertions, 0 deletions