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 14/16] docs: describe virtio-sound capture options
Date: Wed, 11 Nov 2026 06:26:38 +0000 [thread overview]
Message-ID: <sashiko-outbox-208439@kernel.org> (raw)
In-Reply-To: <20261111025655.63951-15-mynameisjune111@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] docs: sound: virtio-snd module parameters omitted in
alsa-configuration.rst
--
commit fc63ed4859aff78c0a8bfa3a6ac071eee34558c9
Author: Joonho Lee <mynameisjune111@gmail.com>
docs: describe virtio-sound capture options
This commit documents virtio-snd capture buffer handling in
Documentation/sound/alsa-configuration.rst and adds entries for the
virtio_snd.capture_packed_status and virtio_snd.capture_pause_restart
parameters in Documentation/admin-guide/kernel-parameters.txt.
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index e75344f4e0cde..ca3fd768b4395 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -8344,6 +8344,20 @@ Kernel parameters
>
> Can be used multiple times for multiple devices.
>
> + virtio_snd.capture_packed_status= [HW,ALSA]
> + Read an explicitly enabled packed status trailer after
> + the returned capture data. The fixed status scatterlist is
> + used by default.
> + Format: <bool>
> + Default: false.
> +
> + virtio_snd.capture_pause_restart= [HW,ALSA]
> + Stop and release the stream when pausing capture. On
> + resume, send PREPARE and START. If disabled, pause uses
> + STOP and START while retaining the prepared stream.
> + Format: <bool>
> + Default: false.
> +
> vga= [BOOT,X86-32] Select a particular video mode
> See Documentation/arch/x86/boot.rst and
> Documentation/admin-guide/svga.rst.
> diff --git a/Documentation/sound/alsa-configuration.rst b/Documentation/sound/alsa-configuration.rst
> index 689eccf6a5921..d40c683abc63e 100644
> --- a/Documentation/sound/alsa-configuration.rst
> +++ b/Documentation/sound/alsa-configuration.rst
> @@ -2537,6 +2537,21 @@ midi_devs
>
> This module supports multiple cards.
>
> +Module virtio-snd
> +-----------------
> +
> +Virtio-sound capture receives data into a separate request buffer for each
> +PCM period. The driver validates the responses and appends frame-aligned audio
> +to the ALSA ring in request order. Valid short responses are retained. Empty
> +responses are accepted only during bounded startup or for requests already in
> +flight at STOP or PAUSE.
> +
> +On MMU systems, the request buffers are vmalloc-backed and page-rounded
> +individually. Allocator rounding can make total additional memory exceed the
> +ALSA ring size, especially with small periods. The request buffers remain
> +allocated from hw_params until hw_free.
> +Captured audio is copied from each request buffer into the ALSA ring.
[Severity: Low]
Should capture_packed_status and capture_pause_restart also be documented
here under the "Module virtio-snd" section?
CONFIG_SND_VIRTIO is tristate and defines these options with
module_param_named() in sound/virtio/virtio_pcm_ops.c, while
Documentation/admin-guide/kernel-parameters.txt directs [HW,ALSA] users
to Documentation/sound/alsa-configuration.rst for per-driver ALSA module
parameters. This new "Module virtio-snd" subsection sits inside the
"Module parameters" section of alsa-configuration.rst, so readers looking
there for the module's parameters will not find capture_packed_status or
capture_pause_restart listed.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111025655.63951-1-mynameisjune111@gmail.com?part=14
next prev parent reply other threads:[~2026-11-11 6:26 UTC|newest]
Thread overview: 21+ 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
2026-11-11 2:56 ` [PATCH v25 14/16] docs: describe virtio-sound capture options Joonho Lee
2026-11-11 6:26 ` sashiko-bot [this message]
2026-11-11 2:56 ` [PATCH v25 15/16] ALSA: virtio: reject invalid playback completions Joonho Lee
2026-11-11 2:56 ` [PATCH v25 16/16] ALSA: virtio: preserve playback progress across pause Joonho Lee
2026-11-11 7:06 ` 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-208439@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