From: Keith Busch <kbusch@kernel.org>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: hch@lst.de, linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [PATCH 2/3] nvme-pci: remove cached shadow doorbell offsets
Date: Fri, 1 May 2020 04:07:48 +0900 [thread overview]
Message-ID: <20200430190748.GA25039@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <16621645-8183-33d7-14d1-8d4c9375e55c@oracle.com>
On Wed, Apr 29, 2020 at 11:36:52PM -0700, Dongli Zhang wrote:
> Hi Keith,
>
> On 4/27/20 4:52 PM, Keith Busch wrote:
> > Real nvme hardware doesn't support the shadow doorbell feature. Remove
>
> I used to test with nvme emulated by qemu and NVME_CTRL_OACS_DBBUF_SUPP is not
> set yet.
>
> Would you please share which emulator would support NVME_CTRL_OACS_DBBUF_SUPP?
Sorry, there is no freely available implementation that I'm aware of.
I think qemu could benefit from this feature, and there had been some
implementation attempts, but nothing that ever made it upstream.
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-04-30 19:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 23:52 [PATCH 1/3] nvme-pci: clear shadow doorbell memory on resets Keith Busch
2020-04-27 23:52 ` [PATCH 2/3] nvme-pci: remove cached shadow doorbell offsets Keith Busch
2020-04-30 6:36 ` Dongli Zhang
2020-04-30 19:07 ` Keith Busch [this message]
2020-05-01 12:54 ` Christoph Hellwig
2021-10-04 9:42 ` John Levon
2020-04-27 23:52 ` [PATCH 3/3] nvme-pci: reshuffle nvme_queue members Keith Busch
2020-05-01 12:57 ` Christoph Hellwig
2020-05-01 15:08 ` Keith Busch
2020-05-01 15:12 ` Christoph Hellwig
2020-05-01 15:23 ` Keith Busch
2020-05-04 18:18 ` Keith Busch
2020-05-01 12:49 ` [PATCH 1/3] nvme-pci: clear shadow doorbell memory on resets Christoph Hellwig
2021-10-04 9:35 ` John Levon
2021-10-06 12:07 ` Keith Busch
2021-10-06 16:05 ` John Levon
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=20200430190748.GA25039@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=dongli.zhang@oracle.com \
--cc=hch@lst.de \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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).