From: Alexander Mikhalitsyn <alexander@mihalicyn.com>
To: qemu-devel@nongnu.org
Cc: "Stéphane Graber" <stgraber@stgraber.org>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>,
"Keith Busch" <kbusch@kernel.org>,
"Klaus Jensen" <its@irrelevant.dk>,
qemu-block@nongnu.org, "Jesper Devantier" <foss@defmacro.it>,
"Alexander Mikhalitsyn" <aleksandr.mikhalitsyn@futurfusion.io>
Subject: [PATCH v3 0/2] hw/nvme: support online resize
Date: Mon, 3 Aug 2026 10:30:44 +0200 [thread overview]
Message-ID: <20260803083046.110121-1-alexander@mihalicyn.com> (raw)
From: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@futurfusion.io>
Dear friends,
This patchset is aimed to support online resize for NVMe emulated
device. My approach is simple - I just implement (BlockDevOps *)->resize_cb()
callback and ensure that AER notification is fired to all controllers using
a namespace that is being resized.
Testing.
I manually validated this with Debian 13 VM (a resized disk was a root disk) and
Windows Server 2022 (a resized disk was a secondary one).
Git tree:
https://gitlab.com/mihalicyn/qemu/-/commits/nvme-resize
Changelog for version 3:
- rebased
Changelog for version 2:
- checkpatch fixes
- rebased
- CI is green (https://gitlab.com/mihalicyn/qemu/-/pipelines/2602102750)
Kind regards,
Alex
Alexander Mikhalitsyn (2):
hw/nvme: initialize ns->subsys for n->namespace
hw/nvme: support online resize
hw/nvme/ctrl.c | 10 ++++++++
hw/nvme/ns.c | 68 +++++++++++++++++++++++++++++++++++++++++++++++++-
hw/nvme/nvme.h | 2 ++
3 files changed, 79 insertions(+), 1 deletion(-)
--
2.47.3
next reply other threads:[~2026-08-03 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 8:30 Alexander Mikhalitsyn [this message]
2026-08-03 8:30 ` [PATCH v3 1/2] hw/nvme: initialize ns->subsys for n->namespace Alexander Mikhalitsyn
2026-08-03 8:30 ` [PATCH v3 2/2] hw/nvme: support online resize Alexander Mikhalitsyn
2026-08-03 13:42 ` [PATCH v3 0/2] " Klaus Jensen
2026-08-31 7:04 ` Alexander Mikhalitsyn
2026-09-07 7:39 ` Klaus Jensen
2026-09-07 8:24 ` Alexander Mikhalitsyn
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=20260803083046.110121-1-alexander@mihalicyn.com \
--to=alexander@mihalicyn.com \
--cc=aleksandr.mikhalitsyn@futurfusion.io \
--cc=foss@defmacro.it \
--cc=its@irrelevant.dk \
--cc=kbusch@kernel.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stgraber@stgraber.org \
/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.