From: sashiko-bot@kernel.org
To: "Joonho Lee" <mynameisjune111@gmail.com>, linux-sound@vger.kernel.org
Cc: virtualization@lists.linux.dev,
"Michael S. Tsirkin" <mst@redhat.com>,
"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v25 16/16] ALSA: virtio: preserve playback progress across pause
Date: Wed, 11 Nov 2026 07:06:12 +0000 [thread overview]
Message-ID: <sashiko-outbox-208492@kernel.org> (raw)
In-Reply-To: <20261111025655.63951-17-mynameisjune111@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] ALSA: virtio: dropped refill in virtsnd_pcm_pb_pointer()
stalls playback
--
commit 4311dfc7324b8614c483b2c630bddb6a93007fbd
Author: Joonho Lee <mynameisjune111@gmail.com>
ALSA: virtio: preserve playback progress across pause
This commit preserves playback completion progress across pause, caches
device latency in substream state, caps indirect hw_queue_size to one period
below the buffer size, and skips period notifications when no playback
progress is pending.
> diff --git a/sound/virtio/virtio_pcm_ops.c b/sound/virtio/virtio_pcm_ops.c
> index 6d6c1bcd8601b..6c11885c55104 100644
> --- a/sound/virtio/virtio_pcm_ops.c
> +++ b/sound/virtio/virtio_pcm_ops.c
> @@ -770,6 +770,13 @@ static int virtsnd_pcm_prepare_locked(struct snd_pcm_substream *substream)
> memset(&vss->pcm_indirect, 0, sizeof(vss->pcm_indirect));
> vss->pcm_indirect.sw_buffer_size = vss->buffer_bytes;
> vss->pcm_indirect.hw_buffer_size = vss->buffer_bytes;
> + if (vss->direction == SNDRV_PCM_STREAM_PLAYBACK) {
> + /* Keep unobserved completions below one physical ring. */
> + vss->pcm_indirect.hw_queue_size = vss->buffer_bytes -
> + snd_pcm_lib_period_bytes(substream);
> + vss->playback_latency_bytes = 0;
> + substream->runtime->delay = 0;
> + }
[Severity: Medium]
Can capping vss->pcm_indirect.hw_queue_size leave the held-back period in
vss->pcm_indirect.sw_ready unsubmitted if virtsnd_pcm_pb_pointer() runs while
runtime->buffer_accessing is temporarily negative?
With hw_queue_size capped at buffer_bytes - period_bytes, filling the buffer
holds the final period in vss->pcm_indirect.sw_ready until
virtsnd_pcm_pb_pointer() calls snd_pcm_indirect_playback_pointer(), which
updates hw_io and hw_ready before invoking substream->ops->ack()
(virtsnd_pcm_pb_ack()).
If a concurrent non-atomic ioctl such as SNDRV_PCM_IOCTL_RESET or
SNDRV_PCM_IOCTL_PREPARE on a running stream calls
snd_pcm_buffer_access_lock() before acquiring the PCM stream lock and being
rejected with -EBUSY, runtime->buffer_accessing is transiently -1:
sound/virtio/virtio_pcm_ops.c:virtsnd_pcm_ack_state() {
...
case SNDRV_PCM_STATE_RUNNING:
case SNDRV_PCM_STATE_PAUSED:
case SNDRV_PCM_STATE_DRAINING:
if (atomic_read(&substream->runtime->buffer_accessing) < 0)
return -EBADFD;
return 0;
...
}
snd_pcm_indirect_playback_pointer() only checks for -EPIPE and ignores
-EBADFD, so vss->pcm_indirect.hw_io advances to vss->hw_ptr without queuing
vss->pcm_indirect.sw_ready. With a two-period buffer or during
SNDRV_PCM_STATE_DRAINING, vss->msg_count reaches 0 with vss->hw_ptr equal to
vss->pcm_indirect.hw_io, virtsnd_pcm_playback_progress_pending() returns
false, and playback or drain stalls.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111025655.63951-1-mynameisjune111@gmail.com?part=16
prev parent reply other threads:[~2026-11-11 7:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 2:56 [PATCH v25 00/16] ALSA: virtio: serialize PCM recovery and preserve capture and playback progress Joonho Lee
2026-11-11 2:56 ` [PATCH v25 01/16] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-11 2:56 ` [PATCH v25 02/16] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-11 2:56 ` [PATCH v25 03/16] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-11 2:56 ` [PATCH v25 04/16] ALSA: pcm: notify drivers after linked prepare completes Joonho Lee
2026-11-11 4:00 ` sashiko-bot
2026-11-11 2:56 ` [PATCH v25 05/16] ALSA: pcm: serialize linked buffer actions Joonho Lee
2026-11-11 2:56 ` [PATCH v25 06/16] ALSA: virtio: propagate playback send failures through ACK Joonho Lee
2026-11-11 2:56 ` [PATCH v25 07/16] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-11 2:56 ` [PATCH v25 08/16] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-11 2:56 ` [PATCH v25 09/16] ALSA: virtio: bound PCM transfers and retain DMA buffers Joonho Lee
2026-11-11 5:34 ` sashiko-bot
2026-11-11 2:56 ` [PATCH v25 10/16] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-11 2:56 ` [PATCH v25 11/16] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-11 2:56 ` [PATCH v25 12/16] ALSA: virtio: use request-owned capture and serialize recovery Joonho Lee
2026-11-11 2:56 ` [PATCH v25 13/16] ALSA: virtio: prioritize capture period work Joonho Lee
[not found] ` <20261111025655.63951-15-mynameisjune111@gmail.com>
2026-11-11 6:26 ` [PATCH v25 14/16] docs: describe virtio-sound capture options sashiko-bot
[not found] ` <20261111025655.63951-17-mynameisjune111@gmail.com>
2026-11-11 7:06 ` sashiko-bot [this message]
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=sashiko-outbox-208492@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=eperezma@redhat.com \
--cc=linux-sound@vger.kernel.org \
--cc=mst@redhat.com \
--cc=mynameisjune111@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
/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