From: Clemens Kolbitsch <clemens.kol@gmx.at>
To: qemu-devel@nongnu.org
Cc: dor.laor@gmail.com
Subject: Re: Re: [Qemu-devel] qcow2 vs. image file format --> pci device
Date: Mon, 1 Oct 2007 10:52:27 +0200 [thread overview]
Message-ID: <200710011052.27998.clemens.kol@gmx.at> (raw)
In-Reply-To: <20070929212408.11071gmx1@mx071.gmx.net>
> 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
next parent reply other threads:[~2007-10-01 8:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070929212408.11071gmx1@mx071.gmx.net>
2007-10-01 8:52 ` Clemens Kolbitsch [this message]
2007-10-01 9:31 ` [Qemu-devel] qcow2 vs. image file format --> pci device Dor Laor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200710011052.27998.clemens.kol@gmx.at \
--to=clemens.kol@gmx.at \
--cc=dor.laor@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).