diff options
| author | Jan H. Schönherr <jschoenh@amazon.de> | 2017-05-20 13:24:32 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2017-05-26 18:01:21 +0200 |
| commit | 52b5419016997f2960e9c8b6584c4acb3875d126 (patch) | |
| tree | 8179887b77543d7caae5653560f5f1c95542e44b /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | e1d39b17e044e8ae819827810d87d809ba5f58c0 (diff) | |
KVM: x86: Fix virtual wire mode
Intel SDM says, that at most one LAPIC should be configured with ExtINT
delivery. KVM configures all LAPICs this way. This causes pic_unlock()
to kick the first available vCPU from the internal KVM data structures.
If this vCPU is not the BSP, but some not-yet-booted AP, the BSP may
never realize that there is an interrupt.
Fix that by enabling ExtINT delivery only for the BSP.
This allows booting a Linux guest without a TSC in the above situation.
Otherwise the BSP gets stuck in calibrate_delay_converge().
Signed-off-by: Jan H. Schönherr <jschoenh@amazon.de>
Reviewed-by: Wanpeng Li <wanpeng.li@hotmail.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions