From: Kevin Wolf <kwolf@redhat.com>
To: Keith Busch <keith.busch@gmail.com>
Cc: "Keith Busch" <keith.busch@intel.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Hannes Reinecke" <hare@suse.de>
Subject: Re: [Qemu-devel] [PATCH] NVMe: Initial commit to add an NVM Express device
Date: Mon, 10 Dec 2012 13:36:05 +0100 [thread overview]
Message-ID: <50C5D735.8070902@redhat.com> (raw)
In-Reply-To: <CAOSXXT6M1++X+68OOZy=y-wFxYhKwutEC_Pf4esg1C_kFZHD0w@mail.gmail.com>
Hi Keith,
Am 08.12.2012 20:20, schrieb Keith Busch:
>> IIUC from the website above, NVMe is to be used with SSDs? It would be
>> good to add to the commit message how to actually use the device
>> command-line-wise beyond the obvious -device nvme: I did not spot on
>> brief sight where you expose a bus to add drives (nor a special IF_*
>> interface type to assign to a drive), so others might wonder as well.
>
> Actually the nvme device _is_ the SSD. The emulated controller here
> creates files to use for its backing storage so you don't add
> additional drives, if that makes sense.
I think the device would be much more useful if you could make it use
the qemu block layer instead of implementing your own functions for only
raw images and only with a given magic file name.
Kevin
next prev parent reply other threads:[~2012-12-10 12:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-08 0:05 [Qemu-devel] [PATCH] NVMe: Initial commit to add an NVM Express device Keith Busch
2012-12-08 7:38 ` Stefan Weil
2012-12-08 7:52 ` Stefan Weil
2012-12-08 17:59 ` Andreas Färber
2012-12-08 19:20 ` Keith Busch
2012-12-08 20:59 ` Andreas Färber
2012-12-10 12:36 ` Kevin Wolf [this message]
2012-12-10 14:11 ` Stefan Hajnoczi
2012-12-10 16:28 ` Busch, Keith
2012-12-13 0:13 ` Busch, Keith
2012-12-13 9:12 ` Kevin Wolf
2012-12-13 9:34 ` Paolo Bonzini
2012-12-13 9:33 ` Paolo Bonzini
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=50C5D735.8070902@redhat.com \
--to=kwolf@redhat.com \
--cc=afaerber@suse.de \
--cc=hare@suse.de \
--cc=keith.busch@gmail.com \
--cc=keith.busch@intel.com \
--cc=mst@redhat.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).