From: Michael Tokarev <mjt@tls.msk.ru>
To: malc <av1474@comtv.ru>
Cc: Jan Kiszka <jan.kiszka@web.de>,
Stefan Pietsch <stefan.pietsch@lsexperts.de>,
kvm@vger.kernel.org, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: KVM: High CPU load with audio enabled
Date: Tue, 09 Nov 2010 17:41:19 +0300 [thread overview]
Message-ID: <4CD95D8F.9030900@msgid.tls.msk.ru> (raw)
In-Reply-To: <4CD95BBE.5000905@msgid.tls.msk.ru>
09.11.2010 17:33, Michael Tokarev wrote:
> 09.11.2010 16:48, malc wrote:
>> On Tue, 9 Nov 2010, Jan Kiszka wrote:
>>
>>> Am 09.11.2010 00:48, Michael Tokarev wrote:
> []
>>>> Yes, sound in 0.13 appears to be broken. It is looping in
>>>> select/read loop forever, read returns EAGAIN and select
>>>> says the filedescriptor is ready.
>>>
>>> Try to set QEMU_AUDIO_DAC_TRY_POLL=0 for the environment of the qemu
>>> process. That's long required to get sound out of the Musicpal emulation
>>> as well (malc, you may recall this). It even got worse with current
>>> qemu.git: previously, the sounds was just quirky. Now the system is
>>> booting way slower in polling mode and is partially not reactive anymore.
>>
>> Wich driver is being used? ALSA stuff should have been fixed by Jindrich
>> Makovicka in:
>> 38cc9b607f85017b095793cab6c129bc9844f441 and
>> 22d948a2d97434192018bdabaf0a50cda7f994be
>
> As far as I can see, both are in 0.13.0 release, which is
> the one I'm running currently.
Ok. This is wrong: neither of the two changes went into any
stable release. Hence we've bugs which are long fixed but
no one knows about this. As usual for qemu[-kvm] development.
/mjt
next prev parent reply other threads:[~2010-11-09 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 12:40 KVM: High CPU load with audio enabled Stefan Pietsch
2010-11-08 16:31 ` lidong chen
2010-11-08 23:48 ` Michael Tokarev
2010-11-09 8:27 ` Jan Kiszka
2010-11-09 13:48 ` malc
2010-11-09 14:33 ` Michael Tokarev
2010-11-09 14:41 ` Michael Tokarev [this message]
2010-11-10 9:39 ` Stefan Pietsch
2010-11-10 10:18 ` Michael Tokarev
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=4CD95D8F.9030900@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=av1474@comtv.ru \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=stefan.pietsch@lsexperts.de \
/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