qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gollu Appalanaidu <anaidu.gollu@samsung.com>
To: Keith Busch <kbusch@kernel.org>
Cc: fam@euphon.net, kwolf@redhat.com, qemu-block@nongnu.org,
	qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
	its@irrelevant.dk
Subject: Re: [PATCH v3] hw/block/nvme: add device self test command support
Date: Mon, 12 Apr 2021 14:02:45 +0530	[thread overview]
Message-ID: <20210412083245.GA24260@2030045822> (raw)
In-Reply-To: <20210412082749.GA24161@2030045822>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

On Mon, Apr 12, 2021 at 01:57:49PM +0530, Gollu Appalanaidu wrote:
>On Sat, Apr 10, 2021 at 12:35:20AM +0900, Keith Busch wrote:
>>On Wed, Mar 31, 2021 at 02:54:27PM +0530, Gollu Appalanaidu wrote:
>>>This is to add support for Device Self Test Command (DST) and
>>>DST Log Page. Refer NVM Express specification 1.4b section 5.8
>>>("Device Self-test command")
>>
>>Please don't write change logs that just say what you did. I can read
>>the code to see that. Explain why this is useful because this frankly
>>looks like another useless feature. We don't need to implement every
>>optional spec feature here. There should be a real value proposition.
>>
>Hi Keith,
>It was useful to us to be able to test the feature against qemu - and
>we wanted to contribute the code, but we understand that features should
>be more "complete" for upstreaming.
>
>New features for SPDK (and nvme-cli) are use-cases for optional features
>like this, where one might not have physical device available and also users
>who is going to develop their in house host test tool this would be useful,
>since we are providing the functional behaviour as per the NVMe protocol.

Hi Keith,

It was useful to us to be able to test the feature against qemu - and
we wanted to contribute the code, but we understand that features should
be more "complete" for upstreaming.

New features for SPDK (and nvme-cli) are use-cases for optional features
like this, where one might not have physical device available and also users
who is going to develop their in house host test tool this would be useful,
since we are providing the functional behaviour as per the NVMe protocol.

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      parent reply	other threads:[~2021-04-12  8:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20210331092753epcas5p33ef9360c0c8c6b6310108d2da9aa2687@epcas5p3.samsung.com>
2021-03-31  9:24 ` [PATCH v3] hw/block/nvme: add device self test command support Gollu Appalanaidu
2021-04-09 15:35   ` Keith Busch
     [not found]     ` <20210412082749.GA24161@2030045822>
2021-04-12  8:32       ` Gollu Appalanaidu [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=20210412083245.GA24260@2030045822 \
    --to=anaidu.gollu@samsung.com \
    --cc=fam@euphon.net \
    --cc=its@irrelevant.dk \
    --cc=kbusch@kernel.org \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).