From: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
To: "its@irrelevant.dk" <its@irrelevant.dk>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>
Cc: "kwolf@redhat.com" <kwolf@redhat.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"k.jensen@samsung.com" <k.jensen@samsung.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"mreitz@redhat.com" <mreitz@redhat.com>
Subject: Re: [PATCH 09/17] hw/block/nvme: flush write cache when disabled
Date: Fri, 3 Jul 2020 00:45:41 +0000 [thread overview]
Message-ID: <7351ad419783cc3e0fbec8db8fd39bfee9f6aa17.camel@wdc.com> (raw)
In-Reply-To: <20200629182642.1170387-10-its@irrelevant.dk>
Looks good,
Reviewed-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
On Mon, 2020-06-29 at 20:26 +0200, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> If the write cache is disabled with a Set Features command, flush it if
> currently enabled.
>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> ---
> hw/block/nvme.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index 39e680a15c56..c2507d8836fd 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -1153,6 +1153,10 @@ static uint16_t nvme_set_feature(NvmeCtrl *n, NvmeCmd *cmd, NvmeRequest *req)
>
> break;
> case NVME_VOLATILE_WRITE_CACHE:
> + if (!(dw11 & 0x1) && blk_enable_write_cache(n->conf.blk)) {
> + blk_flush(n->conf.blk);
> + }
> +
> blk_set_enable_write_cache(n->conf.blk, dw11 & 1);
> break;
> case NVME_NUMBER_OF_QUEUES:
next prev parent reply other threads:[~2020-07-03 0:52 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 18:26 [PATCH 00/17] hw/block/nvme: bump to v1.3 Klaus Jensen
2020-06-29 18:26 ` [PATCH 01/17] hw/block/nvme: bump spec data structures " Klaus Jensen
2020-07-03 0:44 ` Dmitry Fomichev
2020-07-03 5:42 ` Klaus Jensen
2020-06-29 18:26 ` [PATCH 02/17] hw/block/nvme: additional tracing Klaus Jensen
2020-07-03 0:44 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 03/17] hw/block/nvme: add support for the abort command Klaus Jensen
2020-07-03 0:44 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 04/17] hw/block/nvme: add temperature threshold feature Klaus Jensen
2020-07-03 0:44 ` Dmitry Fomichev
2020-07-03 5:45 ` Klaus Jensen
2020-06-29 18:26 ` [PATCH 05/17] hw/block/nvme: mark fw slot 1 as read-only Klaus Jensen
2020-07-03 0:44 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 06/17] hw/block/nvme: add support for the get log page command Klaus Jensen
2020-07-03 0:45 ` Dmitry Fomichev
2020-07-03 5:51 ` Klaus Jensen
2020-06-29 18:26 ` [PATCH 07/17] hw/block/nvme: add support for the asynchronous event request command Klaus Jensen
2020-07-03 0:45 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 08/17] hw/block/nvme: move NvmeFeatureVal into hw/block/nvme.h Klaus Jensen
2020-07-03 0:45 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 09/17] hw/block/nvme: flush write cache when disabled Klaus Jensen
2020-07-03 0:45 ` Dmitry Fomichev [this message]
2020-06-29 18:26 ` [PATCH 10/17] hw/block/nvme: fix missing endian conversion Klaus Jensen
2020-07-03 0:45 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 11/17] hw/block/nvme: add remaining mandatory controller parameters Klaus Jensen
2020-07-03 0:46 ` Dmitry Fomichev
2020-07-03 5:52 ` Klaus Jensen
2020-06-29 18:26 ` [PATCH 12/17] hw/block/nvme: support the get/set features select and save fields Klaus Jensen
2020-07-03 0:46 ` Dmitry Fomichev
2020-07-03 6:03 ` Klaus Jensen
2020-06-29 18:26 ` [PATCH 13/17] hw/block/nvme: make sure ncqr and nsqr is valid Klaus Jensen
2020-07-03 0:46 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 14/17] hw/block/nvme: support identify namespace descriptor list Klaus Jensen
2020-07-03 0:46 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 15/17] hw/block/nvme: enforce valid queue creation sequence Klaus Jensen
2020-07-03 0:47 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 16/17] hw/block/nvme: provide the mandatory subnqn field Klaus Jensen
2020-07-03 0:47 ` Dmitry Fomichev
2020-06-29 18:26 ` [PATCH 17/17] hw/block/nvme: bump supported version to v1.3 Klaus Jensen
2020-07-03 0:47 ` Dmitry Fomichev
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=7351ad419783cc3e0fbec8db8fd39bfee9f6aa17.camel@wdc.com \
--to=dmitry.fomichev@wdc.com \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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 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).