mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Joonho Lee <mynameisjune111@gmail.com>
To: linux-sound@vger.kernel.org
Cc: tiwai@suse.com, perex@perex.cz, anton.yakovlev@opensynergy.com,
	mst@redhat.com, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org, corbet@lwn.net,
	skhan@linuxfoundation.org, rdunlap@infradead.org,
	linux-doc@vger.kernel.org
Subject: [PATCH v20 00/12] ALSA: virtio: fix capture accounting
Date: Sat,  7 Nov 2026 23:34:10 +0900	[thread overview]
Message-ID: <20261107143422.29319-1-mynameisjune111@gmail.com> (raw)

Hi Takashi,

This cumulative resend keeps the twelve-patch series on the same base,
a4311e9447bbb219044db38897f95be112f46a8a. It covers PCM stop-threshold
sampling, locked partial-progress reporting, the optional reset operation,
VirtIO ACK error propagation and recovery, PCM and control DMA ownership,
signal-safe teardown, staged capture lifecycle and work prioritization, and
capture parameter documentation.

Relative to v19, patch 6 moves the virtqueue initialization summary into the
commit body and removes the unsupported event-message ownership claim. Its
source diff is unchanged. Patch 7 also rejects ordinary indirect capture
appl_ptr advances that are not aligned to runtime->min_align before converting
the frame delta to bytes.

Validation:

- The final ARM64 W=1 build uses KASAN, PROVE_LOCKING, and LOCKDEP. The
  cumulative stage build checks patches 7–12 incrementally.
- A synthetic exact-validator case rejects an odd frame delta for 4-bit
  samples before indirect accounting changes. An aligned sub-byte delta and a
  byte-aligned frame delta pass. QEMU does not advertise IMA_ADPCM, so the
  sub-byte case uses synthetic runtime geometry rather than a real stream.
- An actual S16_LE capture accepts two half-period ACKs for one completed
  period and then recovers a full-period read.
- Ordinary and staged capture passed RW and MMAP reset/reopen runs. The
  14-segment oracle matched the QEMU sample sequence.
- Inherited v19 raw SYNC_PTR and paused-lifecycle evidence covers the existing
  accounting state machine. The transport timeout and PCI evidence covers
  unchanged control and teardown paths; these references are listed in the
  manifest.

No physical-device validation or KCSAN run was performed.

Previous version:
https://lore.kernel.org/r/20261106161838.94308-1-mynameisjune111@gmail.com/

AI assistance was used for analysis, implementation, and test preparation.
Assisted-by: LLM

Thanks,
Joonho

base-commit: a4311e9447bbb219044db38897f95be112f46a8a

             reply	other threads:[~2026-11-07 14:34 UTC|newest]

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

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=20261107143422.29319-1-mynameisjune111@gmail.com \
    --to=mynameisjune111@gmail.com \
    --cc=anton.yakovlev@opensynergy.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=perex@perex.cz \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=tiwai@suse.com \
    --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

all inboxes | Powered by JetHome®