On 10/04/2011 03:47 PM, Christian Borntraeger wrote:
Something like the following?
s390: Fix cpu shutdown for KVM
On s390 a shutdown is the state of all CPUs being either stopped
or disabled (for interrupts) waiting. We have to track this number
to call the shutdown sequence accordingly. This p
On 04/10/11 15:56, Peter Maydell wrote:
> On 4 October 2011 14:47, Christian Borntraeger wrote:
>> + * We can only deliver interrupts to (interrupt) enabled CPUs.
>> + * We dont call kvm_s390_add_running_cpu here, since CPUs in enabled
>> wait
>> + * will wait inside the kernel (no ex
On 4 October 2011 14:47, Christian Borntraeger wrote:
> + * We can only deliver interrupts to (interrupt) enabled CPUs.
> + * We dont call kvm_s390_add_running_cpu here, since CPUs in enabled wait
> + * will wait inside the kernel (no exit). Therefore, the targeted
> + * CPUs was n
Something like the following?
s390: Fix cpu shutdown for KVM
On s390 a shutdown is the state of all CPUs being either stopped
or disabled (for interrupts) waiting. We have to track this number
to call the shutdown sequence accordingly. This patch implements
the counting and shutdown handling for
On 10/04/2011 01:28 PM, Christian Borntraeger wrote:
qemu/kvm on s390 currently hangs on panic (doesnt exit on disabled
wait) and also shuts down on cpu hot-unplug (SIGP stop).
This patch tries to fix these simple cases.
On s390 a shutdown is the state of all CPUs being either stopped
or disabled
qemu/kvm on s390 currently hangs on panic (doesnt exit on disabled
wait) and also shuts down on cpu hot-unplug (SIGP stop).
This patch tries to fix these simple cases.
On s390 a shutdown is the state of all CPUs being either stopped
or disabled (for interrupts) waiting. We have to track this number
