diff options
| author |   Paolo Bonzini <pbonzini@redhat.com> | 2015-07-30 13:30:03 +0200 |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-07-30 13:30:03 +0200 |
| commit | 7307f70c6d525aa050d3027035215fb5473aa1bb (patch) | |
| tree | e0bece33b84a5585337ec592e311c84cef551590 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | Merge tag 'for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma (diff) | |
| parent | KVM: s390: Fix hang VCPU hang/loop regression (diff) | |
| download | wireguard-linux-7307f70c6d525aa050d3027035215fb5473aa1bb.tar.xz wireguard-linux-7307f70c6d525aa050d3027035215fb5473aa1bb.zip | |
Merge tag 'kvm-s390-master-20150730' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into kvm-master
KVM: s390: bugfix for kvm/master (4.2)
Here is a bugfix for a regression that was introduced after 4.1
with the commit commit 785dbef407d8 ("KVM: s390: optimize round
trip time in request handling"). After lots of cpu hotplugs in the
guest (online/offline) sometimes a guest CPU did loop within host
KVM code. Reason was that PROG_REQUEST was set in the sie control
block, but no request was pending. This made commit 785dbef407d8
the suspect and changing that area to always reset PROG_REQUEST
did indeed fix the problem.
Special thanks to David Hildenbrand, who helped understanding the
exact sequence that led to the problem.
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions