From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N6cEG-00043e-HR for qemu-devel@nongnu.org; Fri, 06 Nov 2009 22:44:44 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N6cEB-00043C-1Z for qemu-devel@nongnu.org; Fri, 06 Nov 2009 22:44:43 -0500 Received: from [199.232.76.173] (port=49534 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N6cEA-000431-OJ for qemu-devel@nongnu.org; Fri, 06 Nov 2009 22:44:38 -0500 Received: from mail2.shareable.org ([80.68.89.115]:49649) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N6cEA-0007ox-CG for qemu-devel@nongnu.org; Fri, 06 Nov 2009 22:44:38 -0500 Date: Sat, 7 Nov 2009 03:44:34 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu Message-ID: <20091107034434.GA5476@shareable.org> References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com> <20091105163702.GC21630@shareable.org> <4AF30129.7080203@us.ibm.com> <200911051820.48878.arnd@arndb.de> <4AF3154F.8090901@redhat.com> <4AF32E78.1040103@us.ibm.com> <4AF3CED1.7080207@redhat.com> <20091106105407.GA17195@shareable.org> <4AF419C4.6030108@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF419C4.6030108@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Mark McLoughlin , Anthony Liguori , Arnd Bergmann , Arnd Bergmann , Juan Quintela , Dustin Kirkland , qemu-devel@nongnu.org, Michael Tsirkin , Avi Kivity Anthony Liguori wrote: > Jamie Lokier wrote: > >Avi Kivity wrote: > > > >>>I know this has been discussed before, but isn't this why there are > >>>things like vfork()? > >>> > >>vfork() doesn't work with threads - it requires that the calling process > >>be halted until exec() is called. > >> > > > >On Linux (NPTL), vfork() is good for this. It only halts the calling > >thread. Other threads continue to run, and when the vfork'd thread > >called exec*(), it doesn't affect the other threads. Of course this > >behaviour isn't portable, but then again, neither is KVM. > > > Yup, see attached program. Here's the output which confirms this is the > case. Before assuming it, you might want to verify that it's the same on all kernels which support KVM (including backports) and all versions of Linux pthreads which might be used. -- Jamie