From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: martin@schrodt.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH 4/4] audio/hda: detect output buffer overruns and underruns
Date: Thu, 19 Apr 2018 15:10:51 +0200 [thread overview]
Message-ID: <20180419131051.11249-5-kraxel@redhat.com> (raw)
In-Reply-To: <20180419131051.11249-1-kraxel@redhat.com>
If some event caused some larger playback hickup the fine-grained timer
adjust isn't able to recover. Use a buffer overruns and underruns as
indicator for that. Reset timer adjust logic in case we detected one.
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
---
hw/audio/hda-codec.c | 22 ++++++++++++++++++++++
hw/audio/trace-events | 2 ++
2 files changed, 24 insertions(+)
diff --git a/hw/audio/hda-codec.c b/hw/audio/hda-codec.c
index f6fb1d0fa0..623021b7c7 100644
--- a/hw/audio/hda-codec.c
+++ b/hw/audio/hda-codec.c
@@ -261,6 +261,13 @@ static void hda_audio_input_cb(void *opaque, int avail)
int64_t to_transfer = audio_MIN(B_SIZE - (wpos - rpos), avail);
+ if (to_transfer == 0) {
+ /* reset timer adjust */
+ st->buft_start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+ trace_hda_audio_underrun(st->node->name);
+ return;
+ }
+
hda_timer_sync_adjust(st, -((wpos - rpos) + to_transfer - (B_SIZE >> 1)));
while (to_transfer) {
@@ -325,6 +332,21 @@ static void hda_audio_output_cb(void *opaque, int avail)
int64_t to_transfer = audio_MIN(wpos - rpos, avail);
+ if (to_transfer == 0) {
+ /* reset timer adjust */
+ st->buft_start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+ trace_hda_audio_underrun(st->node->name);
+ return;
+ }
+ if (wpos - rpos == B_SIZE) {
+ /* drop buffer, reset timer adjust */
+ st->rpos = 0;
+ st->wpos = 0;
+ st->buft_start = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+ trace_hda_audio_overrun(st->node->name);
+ return;
+ }
+
hda_timer_sync_adjust(st, (wpos - rpos) - to_transfer - (B_SIZE >> 1));
while (to_transfer) {
diff --git a/hw/audio/trace-events b/hw/audio/trace-events
index 30112d97c4..3b2ea2727b 100644
--- a/hw/audio/trace-events
+++ b/hw/audio/trace-events
@@ -22,3 +22,5 @@ milkymist_ac97_out_cb_transferred(int transferred) "transferred %d"
hda_audio_running(const char *stream, int nr, bool running) "st %s, nr %d, run %d"
hda_audio_format(const char *stream, int chan, const char *fmt, int freq) "st %s, %d x %s @ %d Hz"
hda_audio_adjust(const char *stream, int pos) "st %s, pos %d"
+hda_audio_overrun(const char *stream) "st %s"
+hda_audio_underrun(const char *stream) "st %s"
--
2.9.3
next prev parent reply other threads:[~2018-04-19 13:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 13:10 [Qemu-devel] [PATCH 0/4] audio/hda: improve windows guest audio quality Gerd Hoffmann
2018-04-19 13:10 ` [Qemu-devel] [PATCH 1/4] audio/hda: create millisecond timers that handle IO Gerd Hoffmann
2018-04-19 13:10 ` [Qemu-devel] [PATCH 2/4] audio/hda: turn some dprintfs into trace points Gerd Hoffmann
2018-04-19 17:00 ` Philippe Mathieu-Daudé
2018-04-19 13:10 ` [Qemu-devel] [PATCH 3/4] audio/hda: tweak timer adjust logic Gerd Hoffmann
2018-04-19 13:10 ` Gerd Hoffmann [this message]
2018-04-23 9:31 ` [Qemu-devel] [PATCH 4/4] audio/hda: detect output buffer overruns and underruns KONRAD Frederic
2018-04-25 13:05 ` Gerd Hoffmann
2018-05-02 9:56 ` KONRAD Frederic
2018-05-11 9:25 ` KONRAD Frederic
2018-05-14 8:05 ` Gerd Hoffmann
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=20180419131051.11249-5-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=martin@schrodt.org \
--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).