From: Klaus Jensen <its@irrelevant.dk>
To: Keith Busch <kbusch@kernel.org>, qemu-devel@nongnu.org
Cc: "Fam Zheng" <fam@euphon.net>, "Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org, "Klaus Jensen" <k.jensen@samsung.com>,
"Naveen Nagar" <naveen.n1@samsung.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Hanna Reitz" <hreitz@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Klaus Jensen" <its@irrelevant.dk>
Subject: [PATCH 0/6] hw/nvme: enhanced protection information (64-bit guard)
Date: Mon, 14 Feb 2022 13:30:23 +0100 [thread overview]
Message-ID: <20220214123029.106404-1-its@irrelevant.dk> (raw)
From: Klaus Jensen <k.jensen@samsung.com>
This adds support for one possible new protection information format
introduced in TP4068 (and integrated in NVMe 2.0): the 64-bit CRC guard
and 48-bit reference tag. This version does not support storage tags.
Like the CRC16 support already present, this uses a software
implementation of CRC64 (so it is naturally pretty slow). But its good
enough for verification purposes.
This goes hand-in-hand with the support that Keith submitted for the
Linux kernel[1].
[1]: https://lore.kernel.org/linux-nvme/20220201190128.3075065-1-kbusch@kernel.org/
Klaus Jensen (3):
hw/nvme: move dif/pi prototypes into dif.h
hw/nvme: move format parameter parsing
hw/nvme: add pi tuple size helper
Naveen Nagar (3):
hw/nvme: add host behavior support feature
hw/nvme: add support for the lbafee hbs feature
hw/nvme: 64-bit pi support
hw/nvme/ctrl.c | 235 +++++++++++++++++++++------
hw/nvme/dif.c | 378 +++++++++++++++++++++++++++++++++----------
hw/nvme/dif.h | 191 ++++++++++++++++++++++
hw/nvme/ns.c | 27 +++-
hw/nvme/nvme.h | 58 +------
hw/nvme/trace-events | 12 +-
include/block/nvme.h | 81 ++++++++--
7 files changed, 774 insertions(+), 208 deletions(-)
create mode 100644 hw/nvme/dif.h
--
2.35.1
next reply other threads:[~2022-02-14 12:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 12:30 Klaus Jensen [this message]
2022-02-14 12:30 ` [PATCH 1/6] hw/nvme: move dif/pi prototypes into dif.h Klaus Jensen
2022-02-14 12:30 ` [PATCH 2/6] hw/nvme: add host behavior support feature Klaus Jensen
2022-02-14 12:30 ` [PATCH 3/6] hw/nvme: move format parameter parsing Klaus Jensen
2022-02-14 12:30 ` [PATCH 4/6] hw/nvme: add support for the lbafee hbs feature Klaus Jensen
2022-02-14 12:30 ` [PATCH 5/6] hw/nvme: add pi tuple size helper Klaus Jensen
2022-02-14 12:30 ` [PATCH 6/6] hw/nvme: 64-bit pi support Klaus Jensen
2022-02-16 21:20 ` Keith Busch
2022-02-16 21:26 ` [PATCH 0/6] hw/nvme: enhanced protection information (64-bit guard) Keith Busch
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=20220214123029.106404-1-its@irrelevant.dk \
--to=its@irrelevant.dk \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=hreitz@redhat.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=naveen.n1@samsung.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).