* Re: Re: [Qemu-devel] qcow2 vs. image file format --> pci device
[not found] <20070929212408.11071gmx1@mx071.gmx.net>
@ 2007-10-01 8:52 ` Clemens Kolbitsch
2007-10-01 9:31 ` Dor Laor
0 siblings, 1 reply; 2+ messages in thread
From: Clemens Kolbitsch @ 2007-10-01 8:52 UTC (permalink / raw)
To: qemu-devel; +Cc: dor.laor
> 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Qemu-devel] qcow2 vs. image file format --> pci device
2007-10-01 8:52 ` Re: [Qemu-devel] qcow2 vs. image file format --> pci device Clemens Kolbitsch
@ 2007-10-01 9:31 ` Dor Laor
0 siblings, 0 replies; 2+ messages in thread
From: Dor Laor @ 2007-10-01 9:31 UTC (permalink / raw)
To: Clemens Kolbitsch; +Cc: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Clemens Kolbitsch wrote:
>> 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 ;-) )??
>
>
All other NIC emulation work without threads. They use select
(qemu_set_fd_handler)
> In what other HW example can I see how to use the SIGIO completion stuff?
>
Actually I had a mistake, qemu use SIGUSR2 for async io and SIGIO for
timer management.
> Clemens
>
>
[-- Attachment #2: Type: text/html, Size: 2131 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-10-01 9:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20070929212408.11071gmx1@mx071.gmx.net>
2007-10-01 8:52 ` Re: [Qemu-devel] qcow2 vs. image file format --> pci device Clemens Kolbitsch
2007-10-01 9:31 ` Dor Laor
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).