From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IcH13-0006Yx-Sh for qemu-devel@nongnu.org; Mon, 01 Oct 2007 04:52:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IcH0x-0006Pi-DB for qemu-devel@nongnu.org; Mon, 01 Oct 2007 04:52:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IcH0x-0006PU-7Y for qemu-devel@nongnu.org; Mon, 01 Oct 2007 04:52:31 -0400 Received: from mail.gmx.net ([213.165.64.20]) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1IcH0w-00082w-M6 for qemu-devel@nongnu.org; Mon, 01 Oct 2007 04:52:31 -0400 From: Clemens Kolbitsch Subject: Re: Re: [Qemu-devel] qcow2 vs. image file format --> pci device Date: Mon, 1 Oct 2007 10:52:27 +0200 References: <20070929212408.11071gmx1@mx071.gmx.net> In-Reply-To: <20070929212408.11071gmx1@mx071.gmx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200710011052.27998.clemens.kol@gmx.at> 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 Cc: dor.laor@gmail.com > Clemens Kolbitsch wrote: > > hi everyone! > > i have a strange problem (at least to me it seems strange :-) ): > > > > i have implemented a pci device (Network IC) and it works just fine when > > using a standard image. however i now want to support snapshotting... > > > > i started to convert my image into the qcow2 format and suddenly my code > > does not work any more... even if i uncomment everything that has to do > > with snapshotting in my code, it still blocks during qemu startup. > > > > the thing that could cause this: i use 2 additional threads in my NIC > > code ... each is working with semaphores that might cause problems. > > > > is there something in particular i have to be careful of when using qcow2 > > file format? > > > > thanks!! > > Qcow2 uses async io which triggers io completion with SIGIO signal. > If you use threads you must mask this (and also SIGALARM, ..) so your > thread won't > take over the main threads handling. > Anyway, using threads is not the standard qemu guideline. Hi, Ok.. thanks! How do I tell Qemu that I use threads (in this case I don't see an easy way around using them... although there is one obviously ;-) )?? In what other HW example can I see how to use the SIGIO completion stuff? Clemens