All of lore.kernel.org
 help / color / mirror / Atom feed
From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Klaus Jensen <its@irrelevant.dk>, Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH V5 4/6] hw/block/nvme: support for multi-controller in subsystem
Date: Sat, 23 Jan 2021 10:02:27 +0900	[thread overview]
Message-ID: <20210123010227.GA2893@localhost.localdomain> (raw)
In-Reply-To: <20210122184236.GA1728586@dhcp-10-100-145-180.wdc.com>

On 21-01-22 10:42:36, Keith Busch wrote:
> On Fri, Jan 22, 2021 at 09:07:34PM +0900, Minwoo Im wrote:
> > index b525fca14103..3dedefb8ebba 100644
> > --- a/hw/block/nvme.c
> > +++ b/hw/block/nvme.c
> > @@ -4435,6 +4435,9 @@ static void nvme_init_ctrl(NvmeCtrl *n, PCIDevice *pci_dev)
> >      strpadcpy((char *)id->mn, sizeof(id->mn), "QEMU NVMe Ctrl", ' ');
> >      strpadcpy((char *)id->fr, sizeof(id->fr), "1.0", ' ');
> >      strpadcpy((char *)id->sn, sizeof(id->sn), n->params.serial, ' ');
> > +
> > +    id->cntlid = n->cntlid;
> 
> cpu_to_le16()? It might be okay to not do that since the only
> requirement is that this is a unique value, but it would be confusing
> for decoding commands that have a controller id field.

Agreed.

Yes, cntlids are allocated in unique values so that functionality has no
problem here.  But, even if so, we should make it have proper value in
Identify data structure with the policy it has to avoid confusing.

Thanks Keith! will fix it :)


  reply	other threads:[~2021-01-23  1:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 12:07 [PATCH V5 0/6] hw/block/nvme: support multi-path for ctrl/ns Minwoo Im
2021-01-22 12:07 ` [PATCH V5 1/6] hw/block/nvme: introduce nvme-subsys device Minwoo Im
2021-01-22 12:07 ` [PATCH V5 2/6] hw/block/nvme: support to map controller to a subsystem Minwoo Im
2021-01-22 12:07 ` [PATCH V5 3/6] hw/block/nvme: add CMIC enum value for Identify Controller Minwoo Im
2021-01-22 12:07 ` [PATCH V5 4/6] hw/block/nvme: support for multi-controller in subsystem Minwoo Im
2021-01-22 18:42   ` Keith Busch
2021-01-23  1:02     ` Minwoo Im [this message]
2021-01-22 12:07 ` [PATCH V5 5/6] hw/block/nvme: add NMIC enum value for Identify Namespace Minwoo Im
2021-01-22 12:07 ` [PATCH V5 6/6] hw/block/nvme: support for shared namespace in subsystem Minwoo Im

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=20210123010227.GA2893@localhost.localdomain \
    --to=minwoo.im.dev@gmail.com \
    --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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.