From: Andrzej Jakowski <andrzej.jakowski@linux.intel.com>
To: keith.busch@intel.com, kwolf@redhat.com, mreitz@redhat.com
Cc: haozhong.zhang@intel.com,
Andrzej Jakowski <andrzej.jakowski@linux.intel.com>,
qemu-block@nongnu.org, stefanha@gmail.com, qemu-devel@nongnu.org,
dgilbert@redhat.com, yi.z.zhang@linux.intel.com,
junyan.he@intel.com
Subject: [PATCH v2 0/1] Enable PMR feature from NVMe 1.4 spec to NVMe driver
Date: Fri, 21 Feb 2020 14:23:26 -0700 [thread overview]
Message-ID: <20200221212327.24616-1-andrzej.jakowski@linux.intel.com> (raw)
Changes since v1:
- provided support for Bit 1 from PMRWBM register instead of Bit 0 to ensure
improved performance in virtualized environment [1] (Stefan)
- added check if pmr size is power of two in size (David)
- addressed cross compilation build problems reported by CI environment
[1]: https://nvmexpress.org/wp-content/uploads/NVM-Express-1_4-2019.06.10-Ratified.pdf
[2]: https://lore.kernel.org/qemu-devel/20200218224811.30050-1-andrzej.jakowski@linux.intel.com/
---
Persistent Memory Region (PMR) is a new optional feature provided in NVMe 1.4
specification. This patch implements initial support for it in NVMe driver.
Andrzej Jakowski (1):
block/nvme: introduce PMR support from NVMe 1.4 spec
hw/block/nvme.c | 165 +++++++++++++++++++++++++++++++++++++++-
hw/block/nvme.h | 5 ++
hw/block/trace-events | 5 ++
include/block/nvme.h | 172 ++++++++++++++++++++++++++++++++++++++++++
4 files changed, 346 insertions(+), 1 deletion(-)
--
2.21.1
next reply other threads:[~2020-02-21 21:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-21 21:23 Andrzej Jakowski [this message]
2020-02-21 21:23 ` [PATCH v2 1/1] block/nvme: introduce PMR support from NVMe 1.4 spec Andrzej Jakowski
2020-02-26 22:00 ` Andrzej Jakowski
2020-03-03 16:25 ` Andrzej Jakowski
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=20200221212327.24616-1-andrzej.jakowski@linux.intel.com \
--to=andrzej.jakowski@linux.intel.com \
--cc=dgilbert@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=junyan.he@intel.com \
--cc=keith.busch@intel.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=yi.z.zhang@linux.intel.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 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.