[virtio-comment] virtio-rpmb - Support NVMe frame specification

[virtio-comment] virtio-rpmb - Support NVMe frame specification

[David Legault]

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

Hello,

The virtio-rpmb specification should perhaps be amended to include the NVMe RPMB frame format which is completely different than the eMMC/UFS format. This may lead to the spec requiring some flags to signal what type of RPMB device the host is providing such that the guests may be able to build frames in the appropriate format for the device.

https://nvmexpress.org/developers/nvme-specification/

See figure 469 of the 1.4a spec found in the link above.

The control frame is a single entity 256 bytes long with optional data (read/write) coming in 512 byte sectors (eMMC/UFS = 256 bytes). All fields are also Little Endian and in a different order.

eMMC/UFS use 512 byte frames (with inline data) with Big Endian fields.

Regards,

David


----------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

[-- Attachment #2: Type: text/html, Size: 4984 bytes --]

[virtio-comment] RE: virtio-rpmb - Support NVMe frame specification

[Huang, Yang]

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

Hi,

You are right. The NVMe RPMB is not compatible with JEDEC RPMB. And it’s not covered by the current virtio rpmb.
I merged the NVMe RPMB into this section during the review last year but was refused because of the mixed endians and other differences.

Since RPMB is optional for NVMe and is not supported by most NVMe in market, we can hold it for a real requirement.


From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-open.org> On Behalf Of David Legault
Sent: Wednesday, June 10, 2020 9:12 AM
To: virtio-comment@lists.oasis-open.org
Subject: [virtio-comment] virtio-rpmb - Support NVMe frame specification

Hello,

The virtio-rpmb specification should perhaps be amended to include the NVMe RPMB frame format which is completely different than the eMMC/UFS format. This may lead to the spec requiring some flags to signal what type of RPMB device the host is providing such that the guests may be able to build frames in the appropriate format for the device.

https://nvmexpress.org/developers/nvme-specification/

See figure 469 of the 1.4a spec found in the link above.

The control frame is a single entity 256 bytes long with optional data (read/write) coming in 512 byte sectors (eMMC/UFS = 256 bytes). All fields are also Little Endian and in a different order.

eMMC/UFS use 512 byte frames (with inline data) with Big Endian fields.

Regards,

David

________________________________
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

[-- Attachment #2: Type: text/html, Size: 8173 bytes --]