aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/exported-sql-viewer.py
diff options
context:
space:
mode:
authorPeter Xu <[email protected]>2020-06-22 18:04:41 -0400
committerPaolo Bonzini <[email protected]>2020-07-08 16:21:39 -0400
commit6abe9c1386e5c86f360e4e8fde8eec95eee77aa3 (patch)
tree92589b76ee796b24b1fd72b554565b30334d6a52 /tools/perf/scripts/python/exported-sql-viewer.py
parent02f5fb2e69f653ef09490d081ef65296a0cbf114 (diff)
KVM: X86: Move ignore_msrs handling upper the stack
MSR accesses can be one of: (1) KVM internal access, (2) userspace access (e.g., via KVM_SET_MSRS ioctl), (3) guest access. The ignore_msrs was previously handled by kvm_get_msr_common() and kvm_set_msr_common(), which is the bottom of the msr access stack. It's working in most cases, however it could dump unwanted warning messages to dmesg even if kvm get/set the msrs internally when calling __kvm_set_msr() or __kvm_get_msr() (e.g. kvm_cpuid()). Ideally we only want to trap cases (2) or (3), but not (1) above. To achieve this, move the ignore_msrs handling upper until the callers of __kvm_get_msr() and __kvm_set_msr(). To identify the "msr missing" event, a new return value (KVM_MSR_RET_INVALID==2) is used for that. Signed-off-by: Peter Xu <[email protected]> Message-Id: <[email protected]> Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions