From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LkJp3-0007lb-Be for qemu-devel@nongnu.org; Thu, 19 Mar 2009 11:06:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LkJoy-0007iy-HO for qemu-devel@nongnu.org; Thu, 19 Mar 2009 11:06:16 -0400 Received: from [199.232.76.173] (port=51961 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LkJoy-0007ir-8Q for qemu-devel@nongnu.org; Thu, 19 Mar 2009 11:06:12 -0400 Received: from mx2.redhat.com ([66.187.237.31]:35999) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LkJox-0005uK-M6 for qemu-devel@nongnu.org; Thu, 19 Mar 2009 11:06:11 -0400 Message-Id: <20090319145705.988576615@localhost.localdomain> Date: Thu, 19 Mar 2009 11:57:05 -0300 From: mtosatti@redhat.com Subject: [Qemu-devel] [patch 0/7] separate thread for io v2 Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Move IO event processing to a separate thread, with a global mutex serializing access to QEMU data structures. This opens the possibility to execute certain operations in parallel, and is necessary to integrate KVM SMP support. Future changes: - make the cpu_single_env history nicer - use signalfd and block IO event signals in the io thread - optimize tcg interaction - implement kvm smp --