From: neil.armstrong@linaro.org
To: dmukhin@ford.com, u-boot@lists.denx.de
Cc: seanga2@gmail.com, sjg@chromium.org, trini@konsulko.com
Subject: Re: [PATCH v3 0/7] few fixes for NVMe and block devices
Date: Mon, 20 Jul 2026 11:33:02 +0200 [thread overview]
Message-ID: <c4cfbd8e-e596-471a-bcce-40147be5ab20@linaro.org> (raw)
In-Reply-To: <20260716223401.378989-1-dmukhin@ford.com>
Hi,
On 7/17/26 00:33, dmukhin@ford.com wrote:
> The series adds few fixes for NVMe subsystem and block device management.
>
> Patch 1 adds FUA support for NVMe devices (original effort in [1]).
> Patch 2 adds plumbing for blk_flush()/blk_dflush().
> Patch 3 introduces NVMe flush command.
> Patch 4 enables `flush` subcommand to all the block-uclass front-end
> commands (ide, nvme, pvblock, sata, scsi, usb, virtio) in one go.
> Patch 5 makes nvme_shutdown() symbol public to enable use of it from
> board_quiesce_devices()
> Patch 6 tiny fixup for QEMU command for manual NVMe tests.
> Patch 7 updates tests for flushing block devices.
Thanks for updating, but now you enable FUA, why do you still add the
flush infrastructure ?
With FUA enabled, calling flush command would be a no-op.
Neil
>
> [1] https://lore.kernel.org/u-boot/20211019104049.v3.1.Ic581ec99f46b6dfa2e0b1922e670a333ac859e82@changeid/
> [2] Link to v2: https://lore.kernel.org/u-boot/20260529034441.2075305-1-dmukhin@ford.com/
> [3] Link to CI: https://github.com/u-boot/u-boot/pull/995
>
> Denis Mukhin (7):
> drivers: nvme: Enable Force Unit Access (FUA)
> drivers: block: Introduce blk_flush()/blk_dflush()
> drivers: nvme: Implement flush command
> cmd: Add flush support for all blk devices
> drivers: nvme: Export nvme_shutdown()
> docs: nvme: Update QEMU command for testing
> tests: add blk_dflush() coverage
>
> arch/sandbox/cpu/os.c | 5 ++++
> cmd/blk_common.c | 17 +++++++++++++
> cmd/blkmap.c | 2 ++
> cmd/ide.c | 1 +
> cmd/nvme.c | 1 +
> cmd/pvblock.c | 1 +
> cmd/sata.c | 1 +
> cmd/scsi.c | 1 +
> cmd/usb.c | 1 +
> cmd/virtio.c | 1 +
> disk/disk-uclass.c | 6 +++++
> doc/develop/driver-model/nvme.rst | 2 +-
> drivers/block/blk-uclass.c | 15 +++++++++++
> drivers/block/sandbox.c | 9 +++++++
> drivers/nvme/nvme.c | 42 +++++++++++++++++++++++++++++++
> drivers/nvme/nvme.h | 12 ++++-----
> drivers/nvme/nvme_apple.c | 1 +
> include/blk.h | 26 +++++++++++++++++++
> include/nvme.h | 11 ++++++++
> include/os.h | 8 ++++++
> include/part.h | 8 ++++++
> test/dm/host.c | 2 ++
> test/dm/mmc.c | 2 ++
> 23 files changed, 167 insertions(+), 8 deletions(-)
>
prev parent reply other threads:[~2026-07-20 9:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-16 22:33 [PATCH v3 0/7] few fixes for NVMe and block devices dmukhin
2026-07-16 22:33 ` [PATCH v3 1/7] drivers: nvme: Enable Force Unit Access (FUA) dmukhin
2026-07-16 22:33 ` [PATCH v3 2/7] drivers: block: Introduce blk_flush()/blk_dflush() dmukhin
2026-07-16 22:33 ` [PATCH v3 3/7] drivers: nvme: Implement flush command dmukhin
2026-07-16 22:33 ` [PATCH v3 4/7] cmd: Add flush support for all blk devices dmukhin
2026-07-16 22:33 ` [PATCH v3 5/7] drivers: nvme: Export nvme_shutdown() dmukhin
2026-07-20 9:42 ` neil.armstrong
2026-07-16 22:34 ` [PATCH v3 6/7] docs: nvme: Update QEMU command for testing dmukhin
2026-07-16 22:34 ` [PATCH v3 7/7] tests: add blk_dflush() coverage dmukhin
2026-07-20 9:33 ` neil.armstrong [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=c4cfbd8e-e596-471a-bcce-40147be5ab20@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=dmukhin@ford.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.