From: Klaus Jensen <its@irrelevant.dk>
To: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Cc: Padmakar Kalghatgi <p.kalghatgi@samsung.com>,
"kbusch@kernel.org" <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"tasleson@redhat.com" <tasleson@redhat.com>,
"tbzatek@redhat.com" <tbzatek@redhat.com>,
"prakash.v@samsung.com" <prakash.v@samsung.com>,
"d.palani@samsung.com" <d.palani@samsung.com>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>,
"k.jensen@samsung.com" <k.jensen@samsung.com>,
"mohit.kap@samsung.com" <mohit.kap@samsung.com>,
"krish.reddy@samsung.com" <krish.reddy@samsung.com>
Subject: Re: libnvme questions
Date: Fri, 9 Apr 2021 07:48:08 +0200 [thread overview]
Message-ID: <YG/qmMKsFIvGuQoX@apples.localdomain> (raw)
In-Reply-To: <BYAPR04MB49656C8E6D8157608DCF73A686739@BYAPR04MB4965.namprd04.prod.outlook.com>
[-- Attachment #1.1: Type: text/plain, Size: 1280 bytes --]
On Apr 9 03:58, Chaitanya Kulkarni wrote:
>On 4/8/21 00:52, Padmakar Kalghatgi wrote:
>> On Wed, Apr 07, 2021 at 11:16:02PM +0000, Chaitanya Kulkarni wrote:
>>> On 4/7/21 05:46, Padmakar Kalghatgi wrote:
>>>> Along with this, we planned to implement the sideband MI command handling in QEMU.
>>> why ?
>>>
>>>
>>>
>> Add MI command emulation and avoid HW dependency for development and
>> testing.
>>
>
>Absolutely not. With this logic we have to implement entire NVMe command
>set.Current QEMU implementation is lean, I'd like to keep that way and not
>bloat it just for the sake of testing unless there is a kernel component
>that is consuming MI interface and I don't think so we will have it
>anytime soon.
>
I don't see why this would bloat the nvme device. The out-of-band
mechanism would necessarily be implemented by a separate qdev device
that would "listen in" on relevant QEMU busses (PCI, nvme-bus). I expect
this to look something along the lines of ipmi_sim.
The QEMU nvme device is a PCI device, I don't see that changing. It can
implement the in-band tunneling mechanism through the NVMe-MI
Send/Receive commands, but the real work would be handed off to the
nvme-mi qdev device.
At least I think that's how I would do it.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-09 5:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 21:14 libnvme questions Tony Asleson
2021-03-08 7:48 ` Chaitanya Kulkarni
2021-03-10 20:48 ` Keith Busch
2021-03-11 4:43 ` Chaitanya Kulkarni
2021-03-12 15:35 ` Tony Asleson
2021-03-12 16:18 ` Keith Busch
[not found] ` <CGME20210407123854epcas5p48217db953741a57d651a8a8bf240ee23@epcas5p4.samsung.com>
2021-04-07 12:38 ` Padmakar Kalghatgi
2021-04-07 23:16 ` Chaitanya Kulkarni
2021-04-08 7:48 ` Padmakar Kalghatgi
2021-04-09 3:58 ` Chaitanya Kulkarni
2021-04-09 5:48 ` Klaus Jensen [this message]
2021-04-12 11:48 ` Padmakar Kalghatgi
2021-04-07 23:19 ` Chaitanya Kulkarni
2021-04-08 7:50 ` Padmakar Kalghatgi
2021-04-07 23:37 ` Keith Busch
2021-04-08 7:51 ` Padmakar Kalghatgi
2021-04-08 16:46 ` Keith Busch
2021-04-12 8:56 ` Padmakar Kalghatgi
2021-04-08 12:09 ` Christoph Hellwig
2021-03-31 14:15 ` Hannes Reinecke
2021-03-31 14:54 ` Keith Busch
2021-03-31 15:29 ` Hannes Reinecke
2021-04-07 21:34 ` Keith Busch
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=YG/qmMKsFIvGuQoX@apples.localdomain \
--to=its@irrelevant.dk \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=d.palani@samsung.com \
--cc=javier.gonz@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=krish.reddy@samsung.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mohit.kap@samsung.com \
--cc=p.kalghatgi@samsung.com \
--cc=prakash.v@samsung.com \
--cc=tasleson@redhat.com \
--cc=tbzatek@redhat.com \
/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).