summaryrefslogtreecommitdiff
path: root/arch/blackfin/mach-bf561
diff options
context:
space:
mode:
authorPaolo Bonzini <pbonzini@redhat.com>2015-07-30 11:30:03 (GMT)
committerPaolo Bonzini <pbonzini@redhat.com>2015-07-30 11:30:03 (GMT)
commit7307f70c6d525aa050d3027035215fb5473aa1bb (patch)
treee0bece33b84a5585337ec592e311c84cef551590 /arch/blackfin/mach-bf561
parent956325bd55bb020e574129c443a2c2c66a8316e7 (diff)
parent586b7ccdb7143b6a9b975d2c6ad52b6ca5c162b9 (diff)
downloadlinux-7307f70c6d525aa050d3027035215fb5473aa1bb.tar.xz
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 'arch/blackfin/mach-bf561')
0 files changed, 0 insertions, 0 deletions