Linux virtualization list
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Joonho Lee" <mynameisjune111@gmail.com>
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH v19 10/12] ALSA: virtio: serialize staged capture lifecycle and defer paused XRUNs
Date: Fri, 06 Nov 2026 19:01:28 +0000	[thread overview]
Message-ID: <sashiko-outbox-202125@kernel.org> (raw)
In-Reply-To: <20261106161838.94308-11-mynameisjune111@gmail.com>

> Use request-owned RX storage and separate produced, observed and
> consumed positions for shared capture clients. Serialize lifecycle
> operations with lifecycle_lock and ACK accounting with the PCM stream
> lock.
> 
> Close ACK admission before any sleeping teardown and keep prepare's gate
> through the core pointer reset. Reject unavailable epochs with -EBADFD.
> Real transfer XRUNs arm stop_operating in ACK and pause/restart
> triggers, so DROP and prepare retire the remaining device state.
> 
> Track RELEASE completion and rearm release_required immediately after a
> successful resume PREPARE. Publish the resumed prepared state before RX
> submission because a device can complete RX before the START response.
> Record suspend state even when the stopped stream has no queued
> messages.
> [ ... ]
> access. DRAINING state alone does not authorize access after prepared
> has been cleared; retain the explicit PAUSED/RELEASED exception.
> 
> Restore full-ring occupancy after active RESET requeues discarded RX requests, including native paused RESET. Keep linked XRUNs latched while PAUSED; publish them after successful resume so the ordinary pointer path stops the running group.
> Signed-off-by: Joonho Lee <mynameisjune111@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261106161838.94308-1-mynameisjune111@gmail.com?part=10


  reply	other threads:[~2026-11-06 19:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 16:18 [PATCH v19 00/12] ALSA: virtio: fix capture accounting Joonho Lee
2026-11-06 16:18 ` [PATCH v19 01/12] ALSA: pcm: mark stop-threshold accesses for capture policy sampling Joonho Lee
2026-11-06 16:28   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 02/12] ALSA: pcm: report partial progress under the stream lock Joonho Lee
2026-11-06 16:30   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 03/12] ALSA: pcm: add an optional reset operation " Joonho Lee
2026-11-06 16:35   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 04/12] ALSA: virtio: Propagate PCM send failures through ACK Joonho Lee
2026-11-06 17:01   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 05/12] ALSA: virtio: Recover PCM state after a failed start Joonho Lee
2026-11-06 17:26   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 06/12] ALSA: virtio: Retain queued messages through device reset Joonho Lee
2026-11-06 17:48   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 07/12] ALSA: virtio: validate indirect capture appl_ptr accounting Joonho Lee
2026-11-06 18:19   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 08/12] ALSA: virtio: Keep control payloads alive through DMA completion Joonho Lee
2026-11-06 18:29   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 09/12] ALSA: virtio: wait through signals for PCM teardown Joonho Lee
2026-11-06 18:45   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 10/12] ALSA: virtio: serialize staged capture lifecycle and defer paused XRUNs Joonho Lee
2026-11-06 19:01   ` sashiko-bot [this message]
2026-11-06 16:18 ` [PATCH v19 11/12] ALSA: virtio: prioritize staged capture period work Joonho Lee
2026-11-06 19:04   ` sashiko-bot
2026-11-06 16:18 ` [PATCH v19 12/12] docs: describe virtio-sound capture options Joonho Lee
2026-11-06 19:14   ` sashiko-bot

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-202125@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --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