diff options
| author | Like Xu <likexu@tencent.com> | 2021-08-02 15:08:50 +0800 |
|---|---|---|
| committer | Peter Zijlstra <peterz@infradead.org> | 2021-08-04 15:16:34 +0200 |
| commit | df51fe7ea1c1c2c3bfdb81279712fdd2e4ea6c27 (patch) | |
| tree | a9c39906aad73f1a0132460c6decb5a274b32e30 /fs | |
| parent | f4b4b45652578357031fbbef7f7a1b04f6fa2dc3 (diff) | |
| download | linux-df51fe7ea1c1c2c3bfdb81279712fdd2e4ea6c27.tar.gz linux-df51fe7ea1c1c2c3bfdb81279712fdd2e4ea6c27.tar.bz2 linux-df51fe7ea1c1c2c3bfdb81279712fdd2e4ea6c27.zip | |
perf/x86/amd: Don't touch the AMD64_EVENTSEL_HOSTONLY bit inside the guest
If we use "perf record" in an AMD Milan guest, dmesg reports a #GP
warning from an unchecked MSR access error on MSR_F15H_PERF_CTLx:
[] unchecked MSR access error: WRMSR to 0xc0010200 (tried to write 0x0000020000110076) at rIP: 0xffffffff8106ddb4 (native_write_msr+0x4/0x20)
[] Call Trace:
[] amd_pmu_disable_event+0x22/0x90
[] x86_pmu_stop+0x4c/0xa0
[] x86_pmu_del+0x3a/0x140
The AMD64_EVENTSEL_HOSTONLY bit is defined and used on the host,
while the guest perf driver should avoid such use.
Fixes: 1018faa6cf23 ("perf/x86/kvm: Fix Host-Only/Guest-Only counting with SVM disabled")
Signed-off-by: Like Xu <likexu@tencent.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Liam Merwick <liam.merwick@oracle.com>
Tested-by: Kim Phillips <kim.phillips@amd.com>
Tested-by: Liam Merwick <liam.merwick@oracle.com>
Link: https://lkml.kernel.org/r/20210802070850.35295-1-likexu@tencent.com
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions