diff options
| author | David Woodhouse <[email protected]> | 2023-01-11 18:06:48 +0000 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2023-01-11 18:32:21 +0000 |
| commit | 23e60258aeafb04e5dd813f03cb0c8ab7b01462a (patch) | |
| tree | 65a89b3df863d272ce0d6677862e6c558b6a5f0c /tools/perf/scripts/python/flamegraph.py | |
| parent | Merge tag 'kvmarm-fixes-6.2-1' of git://git.kernel.org/pub/scm/linux/kernel/g... (diff) | |
| download | kernel-23e60258aeafb04e5dd813f03cb0c8ab7b01462a.tar.gz kernel-23e60258aeafb04e5dd813f03cb0c8ab7b01462a.zip | |
KVM: x86/xen: Fix lockdep warning on "recursive" gpc locking
In commit 5ec3289b31 ("KVM: x86/xen: Compatibility fixes for shared runstate
area") we declared it safe to obtain two gfn_to_pfn_cache locks at the same
time:
/*
* The guest's runstate_info is split across two pages and we
* need to hold and validate both GPCs simultaneously. We can
* declare a lock ordering GPC1 > GPC2 because nothing else
* takes them more than one at a time.
*/
However, we forgot to tell lockdep. Do so, by setting a subclass on the
first lock before taking the second.
Fixes: 5ec3289b31 ("KVM: x86/xen: Compatibility fixes for shared runstate area")
Suggested-by: Peter Zijlstra <[email protected]>
Signed-off-by: David Woodhouse <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions