From: Klaus Jensen <its@irrelevant.dk>
To: Padmakar Kalghatgi <p.kalghatgi@samsung.com>
Cc: fam@euphon.net, kwolf@redhat.com, arun.kka@samsung.com,
jg123.choi@samsung.com, qemu-block@nongnu.org,
k.jensen@samsung.com, d.palani@samsung.com,
qemu-devel@nongnu.org, linux-nvme@lists.infradead.org,
mreitz@redhat.com, u.kishore@samsung.com, stefanha@redhat.com,
kbusch@kernel.org, javier.gonz@samsung.com,
prakash.v@samsung.com, mohit.kap@samsung.com
Subject: Re: [RFC PATCH: v3 1/2] add mi device in qemu
Date: Wed, 18 Aug 2021 08:01:03 +0200 [thread overview]
Message-ID: <YRyiH7aLzBh/Cko5@apples.localdomain> (raw)
In-Reply-To: <1627975487-1640-1-git-send-email-p.kalghatgi@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 2367 bytes --]
On Aug 3 12:54, Padmakar Kalghatgi wrote:
> From: padmakar <p.kalghatgi@samsung.com>
>
> This patch contains the implementation of certain commands
> of nvme-mi specification.The MI commands are useful to
> manage/configure/monitor the device.Eventhough the MI commands
> can be sent via the inband NVMe-MI send/recieve commands, the idea
> here is to emulate the sideband interface for MI.
>
> The changes here includes the interface for i2c/smbus
> for nvme-mi protocol. We have used i2c address of 0x15
> using which the guest VM can send and recieve the nvme-mi
> commands. Since the nvme-mi device uses the I2C_SLAVE as
> parent, we have used the send and recieve callbacks by
> which the nvme-mi device will get the required notification.
> With the callback approach, we have eliminated the use of
> threads.
>
> One needs to specify the following command in the launch to
> specify the nvme-mi device, link to nvme and assign the i2c address.
> <-device nvme-mi,nvme=nvme0,address=0x15>
>
> This module makes use of the NvmeCtrl structure of the nvme module,
> to fetch relevant information of the nvme device which are used in
> some of the mi commands. Eventhough certain commands might require
> modification to the nvme module, currently we have currently refrained
> from making changes to the nvme module.
>
> cmd-name cmd-type
> *************************************************
> read nvme-mi ds nvme-mi
> configuration set nvme-mi
> configuration get nvme-mi
> vpd read nvme-mi
> vpd write nvme-mi
> controller Health Staus Poll nvme-mi
> nvme subsystem health status poll nvme-mi
> identify nvme-admin
> get log page nvme-admin
> get features nvme-admin
>
> Signed-off-by: Padmakar Kalghatgi <p.kalghatgi@samsung.com>
> Reviewed-by: Klaus Birkelund Jensen <k.jensen@samsung.com>
> Reviewed-by: Jaegyu Choi <jg123.choi@samsung.com>
>
My Reviewed-by here was added by mistake. I've not given it my formal
R-b, but I'll provide a proper review on-list ASAP.
But just glossing over it, I like this approach a lot better than v1
(vsock).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-08-18 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210803080737epcas5p1c9bd6ecde8700d1194748533a3812db6@epcas5p1.samsung.com>
2021-08-03 7:24 ` [RFC PATCH: v3 1/2] add mi device in qemu Padmakar Kalghatgi
[not found] ` <CGME20210803094723epcas5p323efa7e40e3d843ff8b91507c48edd17@epcas5p3.samsung.com>
2021-08-03 9:04 ` [RFC PATCH : v3 2/2] Implementation of nvme-mi plugin in nvme-cli Mohit Kapoor
2021-09-06 14:18 ` Mohit Kapoor
2021-08-18 6:01 ` Klaus Jensen [this message]
2021-08-19 16:34 ` [RFC PATCH: v3 1/2] add mi device in qemu Padmakar Kalghatgi
2021-09-29 4:37 ` Klaus Jensen
2021-10-01 15:15 ` Padmakar Kalghatgi
2021-10-26 13:13 ` [RFC PATCH: v4 " Padmakar Kalghatgi
2021-10-27 5:36 ` [RFC PATCH: v4 2/2] separate utility for nvme-mi Arun Kumar Kashinath Agasar
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=YRyiH7aLzBh/Cko5@apples.localdomain \
--to=its@irrelevant.dk \
--cc=arun.kka@samsung.com \
--cc=d.palani@samsung.com \
--cc=fam@euphon.net \
--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.infradead.org \
--cc=mohit.kap@samsung.com \
--cc=mreitz@redhat.com \
--cc=p.kalghatgi@samsung.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).