From: P J P <ppandit@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Intel HDA and ALSA audio driver hogging event loop
Date: Thu, 20 Oct 2016 14:38:49 +0530 (IST) [thread overview]
Message-ID: <alpine.LFD.2.20.1610201435270.8906@wniryva> (raw)
In-Reply-To: <CAJSP0QUSdfBXMwUL4R2TbtSAXr+jaPUOcnhU4WEPf2AyOKygYg@mail.gmail.com>
Hello Gerd,
+-- On Thu, 20 Oct 2016, Stefan Hajnoczi wrote --+
| A RHEL 7.2 guest sometimes hangs when I play back a wav file on the
| Intel HDA emulated sound card using the QEMU ALSA audio driver.
|
| intel_hda_xfer() transfers samples between the emulated card and the
| QEMU audio subsystem. The following case causes a problem:
| if (st->ctl & (1 << 26)) {
| /*
| * Wait with the next DMA xfer until the guest
| * has acked the buffer completion interrupt
| */
| return false;
| }
|
| If the guest hasn't acked the interrupt yet then Intel HDA returns
| without providing any samples. The QEMU ALSA driver keeps monitoring
| the file descriptor so the next event loop iteration will try to
| transfer samples again.
I was looking at another loop issue in 'intel_hda_xfer'
-> https://lists.gnu.org/archive/html/qemu-devel/2016-10/msg04682.html
It does not address the above case, but maybe both could be fixed together.
Thank you.
--
Prasad J Pandit / Red Hat Product Security Team
47AF CE69 3A90 54AA 9045 1053 DD13 3D32 FE5B 041F
next prev parent reply other threads:[~2016-10-20 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 8:40 [Qemu-devel] Intel HDA and ALSA audio driver hogging event loop Stefan Hajnoczi
2016-10-20 9:08 ` P J P [this message]
2016-10-20 9:38 ` Stefan Hajnoczi
2016-11-04 10:35 ` Stefan Hajnoczi
2016-11-04 12:55 ` Gerd Hoffmann
2016-11-04 13:01 ` Stefan Hajnoczi
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=alpine.LFD.2.20.1610201435270.8906@wniryva \
--to=ppandit@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).