From: Markus Armbruster <armbru@redhat.com>
To: malc <av1474@comtv.ru>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Questions on audio_atexit(), possibly bugs
Date: Sat, 03 Oct 2009 13:47:47 +0200 [thread overview]
Message-ID: <87ab08itr0.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0910030124240.3711@linmac.oyster.ru> (malc's message of "Sat\, 3 Oct 2009 01\:26\:36 +0400 \(MSD\)")
malc <av1474@comtv.ru> writes:
> On Fri, 2 Oct 2009, Markus Armbruster wrote:
[...]
>> Thanks. Next question: I'm having difficulties understanding how
>> HWVoiceIn / HWVoiceOut member enabled works.
>>
>> AUD_set_active_out(), AUD_set_active_in() and audio_run_out() take care
>> to maintain hw->enabled reflecting the state of the voice. They also
>> use it to avoid changing the state uselessly.
>>
>> audio_vm_change_state_handler() uses hw->enabled the same way. But it
>> doesn't update it. Why? Same for audio_atexit().
>>
>
> Because it's more or less a hack, just to make sure host doesn't loop
> the sample it has. Cleaner approach would be to have a member named
> something like tmporarily_disabled or paused, but that's an overkill.
I think I understand why we disable voices on stop. My question is why
we don't record the fact in hw->enabled. Care to explain?
> After some thinking i believe not calling VOICE_DISABLE in atexit is
> possible given that s->vm_running is zero.
Is it? We call exit() in many, many places...
next prev parent reply other threads:[~2009-10-03 11:48 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
2009-10-02 17:04 ` Markus Armbruster
2009-10-02 21:26 ` malc
2009-10-03 11:47 ` Markus Armbruster [this message]
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=87ab08itr0.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=av1474@comtv.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.