From: malc <av1474@comtv.ru>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Questions on audio_atexit(), possibly bugs
Date: Thu, 1 Oct 2009 03:22:04 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0910010316150.26572@linmac.oyster.ru> (raw)
In-Reply-To: <871vlo9gz5.fsf@pike.pond.sub.org>
On Thu, 1 Oct 2009, Markus Armbruster wrote:
> malc <av1474@comtv.ru> writes:
>
> > On Wed, 30 Sep 2009, Markus Armbruster wrote:
> >
> >> Excuse my ignorance on all things audio, but I stumbled over something
> >> that could be wrong.
> >>
> >> audio_vm_change_state_handler() stops voices when the VM stops, and
> >> starts them when it continues.
> >>
> >> audio_atexit() unconditionally stops them. When a stopped VM exits,
> >> this stops voices that are already stopped.
> >>
> >> Does the audio driver contract allow stopping a stopped voice? If yes,
> >> I figured starting a running voice is fine, too. If no, we have a bug
> >> in audio_atexit().
> >
> > This should answer the question audio_atexit existed long before vm
> > change state handlers. Those were actually added to stop the host from
> > looping the same audio fragment over and over again (can/will happen
> > with DirectSound, mmapped OSS, fmod too if i'm not mistaken).
>
> Just to make sure: Does this mean implementations of audio_pcm_ops need
> to cope with stopping a stopped voice?
Yes.
[..snip..]
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-09-30 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 21:39 [Qemu-devel] Questions on audio_atexit(), possibly bugs Markus Armbruster
2009-09-30 22:42 ` malc
2009-09-30 22:59 ` Markus Armbruster
2009-09-30 23:22 ` malc [this message]
2009-10-02 17:04 ` Markus Armbruster
2009-10-02 21:26 ` malc
2009-10-03 11:47 ` Markus Armbruster
2009-10-03 12:21 ` malc
2009-10-03 12:49 ` Markus Armbruster
2009-10-03 12:55 ` malc
2009-09-30 23:28 ` malc
2009-10-01 15:21 ` Markus Armbruster
2009-10-01 21:26 ` malc
2009-10-01 22:40 ` Markus Armbruster
2009-10-01 22:49 ` malc
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=Pine.LNX.4.64.0910010316150.26572@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=armbru@redhat.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).