qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] coroutine-ucontext broken for x86-32


From: Jan Kiszka
Subject: [Qemu-devel] coroutine-ucontext broken for x86-32
Date: Tue, 08 May 2012 16:35:50 -0300
User-agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666

Hi,

I hunted down a fairly subtle corruption of the VCPU thread signal mask
in KVM mode when using the ucontext version of coroutines:

coroutine_new calls getcontext, makecontext, swapcontext. Those
functions get/set also the signal mask of the caller. Unfortunately,
they only use the sigprocmask syscall on i386, not the rt_sigprocmask
version. So they do not properly save/restore the blocked RT signals,
namely our SIG_IPI - it becomes unblocke this way. And this will sooner
or later make the kernel actually deliver a SIG_IPI to our
dummy_handler, and we miss a wakeup, which means losing control over
VCPU thread - qemu hangs.

I was able to reproduce the issue very reliably with virtio-block
enabled, 32-bit qemu userspace on a 64-bit host, using a 32-bit WinXP
guest.

Simple workaround:

diff --git a/main-loop.h b/main-loop.h
index c06b8bc..dce1cd9 100644
--- a/main-loop.h
+++ b/main-loop.h
@@ -25,11 +25,7 @@
 #ifndef QEMU_MAIN_LOOP_H
 #define QEMU_MAIN_LOOP_H 1
 
-#ifdef SIGRTMIN
-#define SIG_IPI (SIGRTMIN+4)
-#else
 #define SIG_IPI SIGUSR1
-#endif
 
 /**
  * qemu_init_main_loop: Set up the process so that it can run the main loop.


But maybe someone has a better idea, ie. something that addresses the
issue at the root. Otherwise we would have to erect large warning signs:
"Do not use RT signals! Coroutines will break them for you."

Michael, maybe this also relates to the issue you saw. I'm not able to
reproduce any VAPIC problems after make Windows bootable by switching
to SIGUSR1.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux



reply via email to

[Prev in Thread] Current Thread [Next in Thread]