diff options
| author | David Hildenbrand <[email protected]> | 2017-04-07 10:50:28 +0200 |
|---|---|---|
| committer | Radim Krčmář <[email protected]> | 2017-04-12 20:17:14 +0200 |
| commit | ba7454e17f90a7dfecc3eb82ec19eb7ac5b6f0e0 (patch) | |
| tree | 9dda398e68130ab68195fa83558bdec78ae8b508 /scripts/gdb/linux/proc.py | |
| parent | 33392b4911150d57cd66a4e9dac74f93b4aef2be (diff) | |
KVM: x86: don't take kvm->irq_lock when creating IRQCHIP
I don't see any reason any more for this lock, seemed to be used to protect
removal of kvm->arch.vpic / kvm->arch.vioapic when already partially
inititalized, now access is properly protected using kvm->arch.irqchip_mode
and this shouldn't be necessary anymore.
Signed-off-by: David Hildenbrand <[email protected]>
Signed-off-by: Radim Krčmář <[email protected]>
Diffstat (limited to 'scripts/gdb/linux/proc.py')
0 files changed, 0 insertions, 0 deletions