From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Klaus Jensen <its@irrelevant.dk>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
Klaus Jensen <k.jensen@samsung.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Keith Busch <kbusch@kernel.org>,
Javier Gonzalez <javier.gonz@samsung.com>,
Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH v2 14/18] hw/block/nvme: support identify namespace descriptor list
Date: Fri, 3 Jul 2020 10:27:19 +0200 [thread overview]
Message-ID: <1a1e7fdf-6e87-aa6b-f687-cc6d98297efe@redhat.com> (raw)
In-Reply-To: <20200703063420.2241014-15-its@irrelevant.dk>
On 7/3/20 8:34 AM, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Since we are not providing the NGUID or EUI64 fields, we must support
> the Namespace UUID. We do not have any way of storing a persistent
> unique identifier, so conjure up a UUID that is just the namespace id.
>
> Signed-off-by: Klaus Jensen <k.jensen@samsung.com>
> Reviewed-by: Dmitry Fomichev <dmitry.fomichev@wdc.com>
> ---
> hw/block/nvme.c | 41 +++++++++++++++++++++++++++++++++++++++++
> hw/block/trace-events | 1 +
> 2 files changed, 42 insertions(+)
>
> diff --git a/hw/block/nvme.c b/hw/block/nvme.c
> index 8230e0e3826b..65c2fa3ac1f4 100644
> --- a/hw/block/nvme.c
> +++ b/hw/block/nvme.c
> @@ -971,6 +971,45 @@ static uint16_t nvme_identify_nslist(NvmeCtrl *n, NvmeIdentify *c)
> return ret;
> }
>
> +static uint16_t nvme_identify_ns_descr_list(NvmeCtrl *n, NvmeIdentify *c)
> +{
> + uint32_t nsid = le32_to_cpu(c->nsid);
> + uint64_t prp1 = le64_to_cpu(c->prp1);
> + uint64_t prp2 = le64_to_cpu(c->prp2);
> +
> + uint8_t list[NVME_IDENTIFY_DATA_SIZE];
> +
> + struct data {
> + struct {
> + NvmeIdNsDescr hdr;
> + uint8_t v[16];
You might consider to use QemuUUID from "qemu/uuid.h". The benefits
are you can use qemu_uuid_parse() qemu_uuid_unparse*() for tracing,
and DEFINE_PROP_UUID() in case you want to set a particular UUID
from command line, it case it is important to the guest.
> + } uuid;
> + };
> +
> + struct data *ns_descrs = (struct data *)list;
> +
> + trace_pci_nvme_identify_ns_descr_list(nsid);
> +
> + if (unlikely(nsid == 0 || nsid > n->num_namespaces)) {
> + trace_pci_nvme_err_invalid_ns(nsid, n->num_namespaces);
> + return NVME_INVALID_NSID | NVME_DNR;
> + }
> +
> + memset(list, 0x0, sizeof(list));
> +
> + /*
> + * Because the NGUID and EUI64 fields are 0 in the Identify Namespace data
> + * structure, a Namespace UUID (nidt = 0x3) must be reported in the
> + * Namespace Identification Descriptor. Add a very basic Namespace UUID
> + * here.
> + */
> + ns_descrs->uuid.hdr.nidt = NVME_NIDT_UUID;
> + ns_descrs->uuid.hdr.nidl = NVME_NIDT_UUID_LEN;
> + stl_be_p(&ns_descrs->uuid.v, nsid);
> +
> + return nvme_dma_read_prp(n, list, NVME_IDENTIFY_DATA_SIZE, prp1, prp2);
> +}
> +
> static uint16_t nvme_identify(NvmeCtrl *n, NvmeCmd *cmd)
> {
> NvmeIdentify *c = (NvmeIdentify *)cmd;
> @@ -982,6 +1021,8 @@ static uint16_t nvme_identify(NvmeCtrl *n, NvmeCmd *cmd)
> return nvme_identify_ctrl(n, c);
> case NVME_ID_CNS_NS_ACTIVE_LIST:
> return nvme_identify_nslist(n, c);
> + case NVME_ID_CNS_NS_DESCR_LIST:
> + return nvme_identify_ns_descr_list(n, c);
> default:
> trace_pci_nvme_err_invalid_identify_cns(le32_to_cpu(c->cns));
> return NVME_INVALID_FIELD | NVME_DNR;
> diff --git a/hw/block/trace-events b/hw/block/trace-events
> index 4a4ef34071df..7b7303cab1dd 100644
> --- a/hw/block/trace-events
> +++ b/hw/block/trace-events
> @@ -45,6 +45,7 @@ pci_nvme_del_cq(uint16_t cqid) "deleted completion queue, cqid=%"PRIu16""
> pci_nvme_identify_ctrl(void) "identify controller"
> pci_nvme_identify_ns(uint32_t ns) "nsid %"PRIu32""
> pci_nvme_identify_nslist(uint32_t ns) "nsid %"PRIu32""
> +pci_nvme_identify_ns_descr_list(uint32_t ns) "nsid %"PRIu32""
> pci_nvme_get_log(uint16_t cid, uint8_t lid, uint8_t lsp, uint8_t rae, uint32_t len, uint64_t off) "cid %"PRIu16" lid 0x%"PRIx8" lsp 0x%"PRIx8" rae 0x%"PRIx8" len %"PRIu32" off %"PRIu64""
> pci_nvme_getfeat(uint16_t cid, uint8_t fid, uint8_t sel, uint32_t cdw11) "cid %"PRIu16" fid 0x%"PRIx8" sel 0x%"PRIx8" cdw11 0x%"PRIx32""
> pci_nvme_setfeat(uint16_t cid, uint8_t fid, uint8_t save, uint32_t cdw11) "cid %"PRIu16" fid 0x%"PRIx8" save 0x%"PRIx8" cdw11 0x%"PRIx32""
>
next prev parent reply other threads:[~2020-07-03 8:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 6:34 [PATCH v2 00/18] hw/block/nvme: bump to v1.3 Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 01/18] hw/block/nvme: bump spec data structures " Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 02/18] hw/block/nvme: additional tracing Klaus Jensen
2020-07-03 8:03 ` Philippe Mathieu-Daudé
2020-07-03 8:14 ` Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 03/18] hw/block/nvme: add support for the abort command Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 04/18] hw/block/nvme: add temperature threshold feature Klaus Jensen
2020-07-03 8:08 ` Philippe Mathieu-Daudé
2020-07-03 8:18 ` Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 05/18] hw/block/nvme: mark fw slot 1 as read-only Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 06/18] hw/block/nvme: add support for the get log page command Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 07/18] hw/block/nvme: add support for the asynchronous event request command Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 08/18] hw/block/nvme: move NvmeFeatureVal into hw/block/nvme.h Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 09/18] hw/block/nvme: flush write cache when disabled Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 10/18] hw/block/nvme: fix missing endian conversion Klaus Jensen
2020-07-03 8:34 ` Philippe Mathieu-Daudé
2020-07-03 10:11 ` Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 11/18] hw/block/nvme: add remaining mandatory controller parameters Klaus Jensen
2020-07-03 8:31 ` Philippe Mathieu-Daudé
2020-07-03 8:46 ` Klaus Jensen
2020-07-03 9:21 ` Philippe Mathieu-Daudé
2020-07-03 10:10 ` Klaus Jensen
2020-07-03 11:02 ` Philippe Mathieu-Daudé
2020-07-03 14:37 ` Klaus Jensen
2020-07-04 21:33 ` Philippe Mathieu-Daudé
2020-07-03 6:34 ` [PATCH v2 12/18] hw/block/nvme: support the get/set features select and save fields Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 13/18] hw/block/nvme: make sure ncqr and nsqr is valid Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 14/18] hw/block/nvme: support identify namespace descriptor list Klaus Jensen
2020-07-03 8:27 ` Philippe Mathieu-Daudé [this message]
2020-07-03 10:00 ` Klaus Jensen
2020-07-03 11:00 ` Philippe Mathieu-Daudé
2020-07-03 6:34 ` [PATCH v2 15/18] hw/block/nvme: reject invalid nsid values in active namespace id list Klaus Jensen
2020-07-03 8:20 ` Philippe Mathieu-Daudé
2020-07-03 8:37 ` Klaus Jensen
2020-07-03 9:14 ` Philippe Mathieu-Daudé
2020-07-03 9:22 ` Klaus Jensen
2020-07-03 10:59 ` Philippe Mathieu-Daudé
2020-07-03 6:34 ` [PATCH v2 16/18] hw/block/nvme: enforce valid queue creation sequence Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 17/18] hw/block/nvme: provide the mandatory subnqn field Klaus Jensen
2020-07-03 8:18 ` Philippe Mathieu-Daudé
2020-07-03 8:25 ` Klaus Jensen
2020-07-03 6:34 ` [PATCH v2 18/18] hw/block/nvme: bump supported version to v1.3 Klaus Jensen
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=1a1e7fdf-6e87-aa6b-f687-cc6d98297efe@redhat.com \
--to=philmd@redhat.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=its@irrelevant.dk \
--cc=javier.gonz@samsung.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mlevitsk@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 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).