From: Keith Busch <kbusch@kernel.org>
To: Klaus Jensen <its@irrelevant.dk>
Cc: Fam Zheng <fam@euphon.net>, Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Gollu Appalanaidu <anaidu.gollu@samsung.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [PATCH v2 5/5] hw/block/nvme: report non-mdts command size limit for dsm
Date: Tue, 23 Feb 2021 05:55:06 +0900 [thread overview]
Message-ID: <20210222205506.GB16253@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <20210222184759.65041-6-its@irrelevant.dk>
On Mon, Feb 22, 2021 at 07:47:59PM +0100, Klaus Jensen wrote:
> +typedef struct NvmeIdCtrlNvm {
> + uint8_t vsl;
> + uint8_t wzsl;
> + uint8_t wusl;
> + uint8_t dmrl;
> + uint32_t dmrsl;
> + uint64_t dmsl;
> + uint8_t rsvd16[4080];
> +} NvmeIdCtrlNvm;
TP 4040a still displays these fields with preceding '...' indicating
something comes before this. Is that just left-over from the integration
for TBD offsets, or is there something that still hasn't been accounted
for?
next prev parent reply other threads:[~2021-02-22 20:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 18:47 [PATCH v2 0/5] hw/block/nvme: misc fixes Klaus Jensen
2021-02-22 18:47 ` [PATCH v2 1/5] hw/block/nvme: remove unnecessary endian conversion Klaus Jensen
2021-02-22 18:47 ` [PATCH v2 2/5] hw/block/nvme: add identify trace event Klaus Jensen
2021-02-22 18:47 ` [PATCH v2 3/5] hw/block/nvme: fix potential compilation error Klaus Jensen
2021-02-22 18:47 ` [PATCH v2 4/5] hw/block/nvme: add trace event for zone read check Klaus Jensen
2021-02-22 18:47 ` [PATCH v2 5/5] hw/block/nvme: report non-mdts command size limit for dsm Klaus Jensen
2021-02-22 20:55 ` Keith Busch [this message]
2021-02-22 21:12 ` Klaus Jensen
2021-03-01 11:15 ` Klaus Jensen
2021-03-01 15:37 ` Keith Busch
2021-03-02 6:23 ` [PATCH v2 0/5] hw/block/nvme: misc fixes 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=20210222205506.GB16253@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=anaidu.gollu@samsung.com \
--cc=fam@euphon.net \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--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 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.