From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org, malc@pulsesoft.com
Subject: [Qemu-devel] SDL audio and AIO hogging each other's signals
Date: Tue, 3 Apr 2007 23:12:32 +0200 [thread overview]
Message-ID: <fb249edb0704031412g7198b6ecp639f8053ade51c30@mail.gmail.com> (raw)
Hi,
with QEMU_AUDIO_DRV set to "sdl" and booting from CD-ROM with AIO on
a Linux host and with SDL 1.2.11, qemu locks up in sigwait() (the main
thread) and SDL_SemWait() (the audio thread) as soon as music is
playing and CD-ROM is being read at the same time. It appears that
audio/sdlaudio.c:sdl_callback is called by SDL when it shouldn't be
called, and block-raw.c is trying to flush the AIO operations, so it
would seem that the SIGUSR2 which is intended to wake up the sigwait
is instead captured by SDL and SDL tries to be smart and calls
sdl_callback. sdl_callback has a sanity check but this check is
*after* SDL_SemWait() so it is not triggered. The strange thing is
that using a different signal (tried SIGUSR1 and SIGPOLL) for AIO
doesn't help. Does SDL catch all signals?
I could be totally wrong because I don't know SDLAudio at all.
Any ideas about the exact reason why this is happening and how to fix it?
Regards,
Andrew
next reply other threads:[~2007-04-03 21:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 21:12 andrzej zaborowski [this message]
2007-04-03 21:56 ` [Qemu-devel] Re: SDL audio and AIO hogging each other's signals malc
2007-04-04 8:26 ` andrzej zaborowski
2007-04-04 11:49 ` malc
2007-04-04 12:23 ` andrzej zaborowski
-- strict thread matches above, loose matches on Subject: below --
2007-04-04 1:44 [Qemu-devel] " Ben Taylor
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=fb249edb0704031412g7198b6ecp639f8053ade51c30@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@gmail.com \
--cc=malc@pulsesoft.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).