From: Stefan Hajnoczi <stefanha@gmail.com>
To: Keith Busch <keith.busch@intel.com>
Cc: qemu-devel@nongnu.org, Keith Busch <keith.busch@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] NVMe: Initial commit
Date: Fri, 19 Apr 2013 11:25:28 +0200 [thread overview]
Message-ID: <20130419092528.GA29826@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1365624994-10219-1-git-send-email-keith.busch@intel.com>
On Wed, Apr 10, 2013 at 02:16:34PM -0600, Keith Busch wrote:
> Initial commit for emulated nvme pci storage device. Implements the
> minimum from the specification to work with existing drivers.
>
> Cc: Keith Busch <keith.busch@gmail.com>
> Signed-off-by: Keith Busch <keith.busch@intel.com>
>
> A lot of people are very interested in this, so I should have more time
> to dedicate working on submitting this upstream. Thanks for the feedback
> on the last round. Only difference here besides the merge-up is making
> the serial option mandatory and a fix for > 4GB backing storage.
> ---
> MAINTAINERS | 5 +
> default-configs/pci.mak | 1 +
> hw/block/Makefile.objs | 1 +
> hw/block/nvme.c | 944 ++++++++++++++++++++++++++++++++++++++++++++++
> hw/block/nvme.h | 712 ++++++++++++++++++++++++++++++++++
> include/hw/pci/pci_ids.h | 1 +
> 6 files changed, 1664 insertions(+), 0 deletions(-)
> create mode 100644 hw/block/nvme.c
> create mode 100644 hw/block/nvme.h
I don't see bdrv_aio_flush() in this patch. How does the guest ensure
that data is safely on persistent storage (e.g. protected against data
loss by power failure).
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4dfd8bf..fbd973e 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -609,6 +609,11 @@ S: Supported
> F: hw/char/virtio-serial-bus.c
> F: hw/char/virtio-console.c
>
> +nvme
> +M: Keith Busch <keith.busch@intel.com>
> +S: Supported
> +F: hw/nvme*
hw/block/nvme*
> +static void nvme_class_init(ObjectClass *oc, void *data)
> +{
> + DeviceClass *dc = DEVICE_CLASS(oc);
> + PCIDeviceClass *pc = PCI_DEVICE_CLASS(oc);
> +
> + pc->init = nvme_init;
> + pc->exit = nvme_exit;
> + pc->class_id = PCI_CLASS_STORAGE_EXPRESS;
> + pc->vendor_id = PCI_VENDOR_ID_INTEL;
> + pc->device_id = 0x5845;
> + pc->subsystem_vendor_id = PCI_VENDOR_ID_INTEL;
> + pc->subsystem_id = 0x1234;
0x1234?
next prev parent reply other threads:[~2013-04-19 9:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 20:16 [Qemu-devel] [PATCH] NVMe: Initial commit Keith Busch
2013-04-11 13:45 ` Jack Wang
2013-04-11 14:01 ` Peter Maydell
2013-04-19 9:25 ` Stefan Hajnoczi [this message]
2013-04-19 14:23 ` Keith Busch
2013-04-19 17:27 ` Stefan Hajnoczi
2013-05-27 14:01 ` Kevin Wolf
2013-05-26 20:41 ` Keith Busch
2013-05-28 15:17 ` Kevin Wolf
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=20130419092528.GA29826@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=keith.busch@gmail.com \
--cc=keith.busch@intel.com \
--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).