Re: [Qemu-devel] [PATCH 1.1] Switch SIG_IPI to SIGUSR1

2012-05-14 Thread Anthony Liguori
On 05/09/2012 05:14 PM, Jan Kiszka wrote: Use SIGUSR1 unconditionally as SIG_IPI. First, ucontext coroutines tend to corrupt RT signal masks due to a 32-on-64-bit Linux kernel bug. And, second, there appears to be no advantage in using RT signals for VCPU kicking. Signed-off-by: Jan Kiszka App

Re: [Qemu-devel] [PATCH 1.1] Switch SIG_IPI to SIGUSR1

2012-05-10 Thread Avi Kivity
On 05/10/2012 01:14 AM, Jan Kiszka wrote: > Use SIGUSR1 unconditionally as SIG_IPI. First, ucontext coroutines tend > to corrupt RT signal masks due to a 32-on-64-bit Linux kernel bug. And, > second, there appears to be no advantage in using RT signals for VCPU > kicking. > > Signed-off-by: Jan Kis

Re: [Qemu-devel] [PATCH 1.1] Switch SIG_IPI to SIGUSR1

2012-05-09 Thread Andreas Färber
Am 10.05.2012 00:14, schrieb Jan Kiszka: > Use SIGUSR1 unconditionally as SIG_IPI. First, ucontext coroutines tend > to corrupt RT signal masks due to a 32-on-64-bit Linux kernel bug. And, > second, there appears to be no advantage in using RT signals for VCPU > kicking. > > Signed-off-by: Jan Kis

[Qemu-devel] [PATCH 1.1] Switch SIG_IPI to SIGUSR1

2012-05-09 Thread Jan Kiszka
Use SIGUSR1 unconditionally as SIG_IPI. First, ucontext coroutines tend to corrupt RT signal masks due to a 32-on-64-bit Linux kernel bug. And, second, there appears to be no advantage in using RT signals for VCPU kicking. Signed-off-by: Jan Kiszka --- As people prefer to stick with ucontext, th