From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:34684) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBhrm-0007Z0-0K for qemu-devel@nongnu.org; Thu, 15 Jan 2015 05:41:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YBhri-0002p1-Mb for qemu-devel@nongnu.org; Thu, 15 Jan 2015 05:41:29 -0500 Received: from [2001:41d0:8:2b42::1] (port=48007 helo=greensocs.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YBhri-0002ol-Eg for qemu-devel@nongnu.org; Thu, 15 Jan 2015 05:41:26 -0500 Message-ID: <54B79954.5010701@greensocs.com> Date: Thu, 15 Jan 2015 11:41:24 +0100 From: Frederic Konrad MIME-Version: 1.0 References: <54B7958D.2040108@greensocs.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] global_mutex and multithread. List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: mttcg@listserver.greensocs.com, Paolo Bonzini , qemu-devel , Alexander Graf On 15/01/2015 11:34, Peter Maydell wrote: > On 15 January 2015 at 10:25, Frederic Konrad wrote: >> Hi everybody, >> >> In case of multithread TCG what is the best way to handle qemu_global_mutex? > It shouldn't need any changes I think. You're basically bringing > TCG into line with what KVM already has -- one thread per guest > CPU; and qemu_global_mutex already works fine in that model. > > -- PMM Hi Peter, Thanks for your reply. True that makes sense, I still think we need to synchronize vcpu when they exit? Fred