From: malc <av1474@comtv.ru>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: Audio
Date: Tue, 15 Sep 2009 01:13:55 +0400 (MSD) [thread overview]
Message-ID: <Pine.LNX.4.64.0909150107090.2297@linmac.oyster.ru> (raw)
In-Reply-To: <4AADE01B.50001@web.de>
On Mon, 14 Sep 2009, Jan Kiszka wrote:
> malc wrote:
> > On Sun, 13 Sep 2009, Jan Kiszka wrote:
> >
> >> Jan Kiszka wrote:
> >>> malc wrote:
> >>>> Does following help?
> >
> > [..snip.]
> >
> >>> Nope, still full CPU load.
> >> Forgot to mention: I also tried OSS before, but it suffered the same
> >> way, and polling had to be disabled.
> >>
> >
> > Aha, i've commited this patch and another which correct premature
> > closure of audio device (for both OSS and ALSA), can not notice
> > anything particularly wrong when running with poll enabled now, can
> > you please retest things on your end, once again it would be nice to
> > have both audio systems, tested. Thanks in advance.
> >
>
> Sorry, both audio systems still require to disable polling for a normal
> cpu load.
I believe the problem is within wm8750(/musicpal combination?)
wm8750_set_format creates a bunch of ADC voices and enables them, but
no reads are ever performed, so ALSA/OSS quickly fills the buffers
and then stops reading into them thus leaving respective fd's in a
selectable state. My main machine lacks ADC so i was unable to reproduce
the behaviour you've seen on it on another box the issue is indeed very
visible. Setting QEMU_OSS_ADC_DEV to /dev/moo or commenting out
AUD_set_active_in in wm8750.c cures the problem as does, contrary to
your report, setting QEMU_AUDIO_ADC_TRY_POLL to 0.
--
mailto:av1474@comtv.ru
next prev parent reply other threads:[~2009-09-14 21:14 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 23:34 [Qemu-devel] Audio malc
2009-09-13 11:30 ` [Qemu-devel] Audio Jan Kiszka
2009-09-13 18:52 ` malc
2009-09-13 19:57 ` Jan Kiszka
2009-09-13 20:07 ` Jan Kiszka
2009-09-14 0:02 ` malc
2009-09-14 6:18 ` Jan Kiszka
2009-09-14 21:13 ` malc [this message]
2009-09-14 21:30 ` [Qemu-devel] Solaris SPARC guest on QEMU Luis Freitas
2009-09-15 6:33 ` Laurent Vivier
2009-09-15 23:31 ` Luis Freitas
2009-09-15 8:55 ` Artyom Tarasenko
2009-09-15 19:19 ` Blue Swirl
2009-09-15 21:08 ` Stuart Brady
2009-09-16 8:28 ` Artyom Tarasenko
2009-09-16 15:38 ` Luis Freitas
2009-09-16 16:33 ` Artyom Tarasenko
2009-09-15 20:11 ` [Qemu-devel] Re: Audio Jan Kiszka
2009-09-18 18:49 ` Jan Kiszka
2009-09-18 19:29 ` malc
2009-09-13 23:31 ` malc
2009-09-15 11:28 ` Avi Kivity
2009-09-22 11:24 ` malc
-- strict thread matches above, loose matches on Subject: below --
2004-11-05 18:47 [Qemu-devel] Audio malc
2004-11-05 20:35 ` [Qemu-devel] Audio Ronald
2004-11-05 20:38 ` André Braga
2004-11-05 20:46 ` malc
[not found] <Pine.LNX.4.55.0410311815320.2162@home.oyster.ru>
2004-11-01 12:32 ` Ronald
2004-11-01 12:43 ` malc
[not found] ` <4185ADFA.7010102@brittainweb.org>
2004-11-01 12:06 ` [Qemu-devel] Audio malc
2004-11-04 17:14 ` Jason Brittain
2004-11-04 19:12 ` [Qemu-devel] Audio Ronald
2004-11-04 19:18 ` Jason Brittain
2004-11-04 19:34 ` Jason Brittain
2004-11-04 20:03 ` malc
2004-11-05 3:22 ` Jason Brittain
2004-11-05 6:28 ` Jens Arm
2004-11-05 8:01 ` Jens Arm
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.0909150107090.2297@linmac.oyster.ru \
--to=av1474@comtv.ru \
--cc=jan.kiszka@web.de \
--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).