From: Padmakar Kalghatgi <p.kalghatgi@samsung.com>
To: Keith Busch <kbusch@kernel.org>
Cc: fam@euphon.net, kwolf@redhat.com, jg123.choi@samsung.com,
qemu-block@nongnu.org, k.jensen@samsung.com,
d.palani@samsung.com, qemu-devel@nongnu.org,
linux-nvme@lists.infrared.org, mreitz@redhat.com,
u.kishore@samsung.com, stefanha@redhat.com, its@irrelevant.dk,
javier.gonz@samsung.com, prakash.v@samsung.com,
mohit.kap@samsung.com
Subject: Re: [RFC PATCH 1/2] hw/nvme: add mi device
Date: Thu, 15 Jul 2021 17:31:58 +0530 [thread overview]
Message-ID: <20210715120158.GA8970@test-zns> (raw)
In-Reply-To: <20210709155842.GA291156@dhcp-10-100-145-180.wdc.com>
[-- Attachment #1: Type: text/plain, Size: 563 bytes --]
On Fri, Jul 09, 2021 at 08:58:42AM -0700, Keith Busch wrote:
>On Fri, Jul 09, 2021 at 07:25:45PM +0530, Padmakar Kalghatgi wrote:
>> The following commands are tested with nvme-cli by hooking
>> to the cid of the vsock as shown above and use the socket
>> send/recieve commands to issue the commands and get the response.
>
>Why sockets? Shouldn't mi targets use smbus for that?
>
vsock mimcs the sideband communication, hence we used it.
However, we are working on the smbus/i2c implementation
for nvme-mi in qemu/nvme-cli, we will send the patch in few days.
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-07-15 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210709135651epcas5p1c544dec5377413bfa4b2eeab6ee43f26@epcas5p1.samsung.com>
2021-07-09 13:55 ` [RFC PATCH 1/2] hw/nvme: add mi device Padmakar Kalghatgi
2021-07-09 15:58 ` Keith Busch
2021-07-15 12:01 ` Padmakar Kalghatgi [this message]
2021-07-12 11:03 ` Stefan Hajnoczi
2021-07-13 5:30 ` Christoph Hellwig
2021-07-13 9:37 ` Stefan Hajnoczi
2021-07-15 14:37 ` Padmakar Kalghatgi
2021-07-15 12:36 ` Padmakar Kalghatgi
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=20210715120158.GA8970@test-zns \
--to=p.kalghatgi@samsung.com \
--cc=d.palani@samsung.com \
--cc=fam@euphon.net \
--cc=its@irrelevant.dk \
--cc=javier.gonz@samsung.com \
--cc=jg123.choi@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=linux-nvme@lists.infrared.org \
--cc=mohit.kap@samsung.com \
--cc=mreitz@redhat.com \
--cc=prakash.v@samsung.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=u.kishore@samsung.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).