From: Keith Busch <keith.busch@intel.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: keith.busch@intel.com, Igor Mammedov <imammedo@redhat.com>,
sahlot arvind <asahlot@gmail.com>,
qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] Quick question on NVME on qemu
Date: Mon, 12 Oct 2015 14:02:51 +0000 (UTC) [thread overview]
Message-ID: <alpine.LNX.2.00.1510121356050.27742@localhost.lm.intel.com> (raw)
In-Reply-To: <20151012084040.GC4153@noname.str.redhat.com>
On Mon, 12 Oct 2015, Kevin Wolf wrote:
> Am 12.10.2015 um 10:05 hat Igor Mammedov geschrieben:
>> On Sat, 10 Oct 2015 00:39:43 -0700
>> sahlot arvind <asahlot@gmail.com> wrote:
>>
>>> Hello,
>>>
>>> Does qemu emulate a proper NVMe controller? Can someone please tell me how
>> s far as I'm aware, QEMU doesn't emulate any NVMe controller yet.
>
> It does, though I'm not sure how complete it is. You can use it with
> -drive file=...,if=none,id=some_id -device nvme,drive=some_id
Yep, that's right. It is a basic 1.0 compliant (mostly) controller. There
are updates for up to 1.2 compliance that are in a public tree, but not
merged to mainline.
http://git.infradead.org/users/kbusch/qemu-nvme.git
>>> can I use it to emulate a proper NVMe controller? Is there some way to
>>> enable logging PCI accesses to NVMe controller so that I can see what
>>> accesses my driver or OS is doing?
It's not a problem to add more NVMe features. There's currently no such
logging mechanism, though. It shouldn't be too difficult to add if you
want to take a stab at it.
prev parent reply other threads:[~2015-10-12 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-10 7:39 [Qemu-devel] Quick question on NVME on qemu sahlot arvind
2015-10-12 8:05 ` Igor Mammedov
2015-10-12 8:40 ` Kevin Wolf
2015-10-12 14:02 ` Keith Busch [this message]
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=alpine.LNX.2.00.1510121356050.27742@localhost.lm.intel.com \
--to=keith.busch@intel.com \
--cc=asahlot@gmail.com \
--cc=imammedo@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).