From: Klaus Jensen <its@irrelevant.dk>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Klaus Jensen <k.jensen@samsung.com>
Subject: [PULL 0/5] hw/nvme fixes
Date: Fri, 20 Nov 2026 13:29:44 +0100 [thread overview]
Message-ID: <20261120122949.1044-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
Hi,
The following changes since commit 08ed97c33c3818ef51a7c852347a28e9f66807b5:
tests/tcg/i386: compile test-i386-blendv.c with -msse4.1 (2026-11-19 13:54:13 -0800)
are available in the Git repository at:
https://gitlab.com/birkelund/qemu.git tags/pull-nvme-20261120
for you to fetch changes up to 7e203726411b7a28b2d020339d6267c7c7d4134e:
hw/nvme: advance zone write pointer only once the write is committed (2026-11-20 11:32:57 +0100)
----------------------------------------------------------------
nvme queue
----------------------------------------------------------------
Klaus Jensen (5):
hw/nvme: report data transfer error on failed dma
hw/nvme: fix zone descriptor extension allocation overflow
hw/nvme: fix open zone zrwa allocation
hw/nvme: bound zrwa flush by the write area and zone write boundary
hw/nvme: advance zone write pointer only once the write is committed
hw/nvme/ctrl.c | 48 +++++++++++++++++++++++++++++++++++-------------
hw/nvme/ns.c | 4 ++--
hw/nvme/nvme.h | 3 ++-
hw/nvme/trace-events | 1 +
4 files changed, 40 insertions(+), 16 deletions(-)
next reply other threads:[~2026-11-20 12:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 12:29 Klaus Jensen [this message]
2026-11-20 12:29 ` [PULL 1/5] hw/nvme: report data transfer error on failed dma Klaus Jensen
2026-11-20 12:29 ` [PULL 2/5] hw/nvme: fix zone descriptor extension allocation overflow Klaus Jensen
2026-11-20 12:29 ` [PULL 3/5] hw/nvme: fix open zone zrwa allocation Klaus Jensen
2026-11-20 12:29 ` [PULL 4/5] hw/nvme: bound zrwa flush by the write area and zone write boundary Klaus Jensen
2026-11-20 12:29 ` [PULL 5/5] hw/nvme: advance zone write pointer only once the write is committed Klaus Jensen
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=20261120122949.1044-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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.