From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:34910) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R61It-0003VG-Et for qemu-devel@nongnu.org; Tue, 20 Sep 2011 10:28:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1R61In-00017f-SP for qemu-devel@nongnu.org; Tue, 20 Sep 2011 10:28:07 -0400 Received: from goliath.siemens.de ([192.35.17.28]:33149) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1R61In-00017T-Gf for qemu-devel@nongnu.org; Tue, 20 Sep 2011 10:28:01 -0400 Message-ID: <4E78A2ED.50401@siemens.com> Date: Tue, 20 Sep 2011 16:27:57 +0200 From: Jan Kiszka MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] qxl: pthread_yield on QXL_IO_NOTIFY_OOM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: qemu-devel Hi Gerd, can you (or anyone familiar with those bits) comment on pthread_yield() in ioport_write() of hw/qxl.c? Which threads are supposed to run this way? Can't this relation be expressed explicitly? If not, can we use a sleep here (how long?)? The background is that yielding easily breaks into pieces when leaving the SCHED_OTHER space (what we are working on). Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux