diff options
author | 2019-10-27 18:52:38 +0800 | |
---|---|---|
committer | 2019-11-15 11:44:06 +0100 | |
commit | 3ca270fc9edb258d5bfa271bcf851614e9e6e7d4 (patch) | |
tree | 4605da2cdbf886dac007befe055832134cf985e4 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | KVM: nVMX: Update vmcs01 TPR_THRESHOLD if L2 changed L1 TPR (diff) | |
download | linux-dev-3ca270fc9edb258d5bfa271bcf851614e9e6e7d4.tar.xz linux-dev-3ca270fc9edb258d5bfa271bcf851614e9e6e7d4.zip |
perf/core: Provide a kernel-internal interface to recalibrate event period
Currently, perf_event_period() is used by user tools via ioctl. Based on
naming convention, exporting perf_event_period() for kernel users (such
as KVM) who may recalibrate the event period for their assigned counter
according to their requirements.
The perf_event_period() is an external accessor, just like the
perf_event_{en,dis}able() and should thus use perf_event_ctx_lock().
Suggested-by: Kan Liang <kan.liang@linux.intel.com>
Signed-off-by: Like Xu <like.xu@linux.intel.com>
Acked-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions