From: Gerd Hoffmann <kraxel@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Bandan Das <bsd@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Make mixer emulation configurable at runtime
Date: Wed, 28 Aug 2013 13:33:42 +0200 [thread overview]
Message-ID: <1377689622.20403.64.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <87bo4igou0.fsf@blackfin.pond.sub.org>
Hi,
> Only pulse and the spice audio backends set VOICE_VOLUME_CAP.
>
> Impact on users isn't obvious to me.
It offloads volume control to the audio backend, i.e. it will be done by
pulseaudio/spice-client instead of mixemu.
> Questions (not just for you, Bandan):
>
> 1. Why is CONFIG_MIXEMU off by default?
malc wants it this way because mixemu eats cpu time.
> 2. Why do we bother providing these devices when CONFIG_MIXEMU off?
>
> Why would anyone want hda audio devices without a mixer? Why
> wouldn't anyone who wants hda audio devices also want CONFIG_MIXEMU
> enabled?
It'll actually work just fine with HDA. The guest figures there is no
volume control and will fallback to do volume control in software then.
Net effect is that the audio sample processing to change volume is done
by the guest instead of mixemu, so you don't actually save cpu time by
turning off mixemu ...
I think AC97 has broken volume control with CONFIG_MIXEMU=n, because the
guest tries to use the non-functional volume controls.
So, yes, for serious sound support you want CONFIG_MIXEMU=y.
cheers,
Gerd
next prev parent reply other threads:[~2013-08-28 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 19:17 [Qemu-devel] [PATCH 0/2] Make mixer emulation configurable at runtime Bandan Das
2013-08-27 19:17 ` [Qemu-devel] [PATCH 1/2] hda-codec: refactor common definitions into a header file Bandan Das
2013-08-28 8:02 ` Markus Armbruster
2013-08-27 19:17 ` [Qemu-devel] [PATCH 2/2] hda-codec: make mixemu selectable at runtime Bandan Das
2013-08-28 9:13 ` [Qemu-devel] [PATCH 0/2] Make mixer emulation configurable " Markus Armbruster
2013-08-28 11:07 ` Paolo Bonzini
2013-08-28 11:33 ` Gerd Hoffmann [this message]
2013-08-28 11:45 ` Markus Armbruster
2013-08-28 11:52 ` Gerd Hoffmann
2013-08-28 15:52 ` Bandan Das
2013-08-28 16:37 ` Markus Armbruster
2013-08-28 17:35 ` Jan Kiszka
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=1377689622.20403.64.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=armbru@redhat.com \
--cc=bsd@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).