From: Paolo Bonzini <pbonzini@redhat.com>
To: Huang Yang <yang.huang@intel.com>, virtio-dev@lists.oasis-open.org
Cc: virtio-comment@lists.oasis-open.org, mst@redhat.com,
bing.zhu@intel.com, tomas.winkler@intel.com
Subject: Re: [virtio-comment] [PATCH] Add virtio rpmb device specification
Date: Mon, 29 Jul 2019 11:19:25 +0200 [thread overview]
Message-ID: <4ecbc7e5-4539-d1f7-eabd-240f5ddd38c5@redhat.com> (raw)
In-Reply-To: <1564386494-2296-1-git-send-email-yang.huang@intel.com>
On 29/07/19 09:48, Huang Yang wrote:
>
> But virtualization software like Qemu doesn't provide eMMC/UFS/NVMe
> RPMB emulation. It blocks the OS like Trusty or OP-TEE running in a
> virtualization environment. For instance, Google right now uses another
> way to work around RPMB emulation issue when running Trusty in ARM Qemu:
> https://android.googlesource.com/trusty/external/trusty/+/refs/heads/master/test-runner/
>
> Virtio RPMB standardization will definitely benefit OP-TEE,
> Google Trusty TEE, Qemu, OVMF or other modules to develop the RPMB
> based secure storage in virtualization.
>
Is there any reason to use a new virtio-blk device, and not add this
functionality to virtio-blk?
Paolo
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2019-07-29 9:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 7:48 [virtio-comment] [PATCH] Add virtio rpmb device specification Huang Yang
2019-07-29 7:48 ` Huang Yang
2019-07-29 14:54 ` [virtio-comment] " Michael S. Tsirkin
2019-07-30 5:51 ` Huang, Yang
2019-07-30 6:49 ` Michael S. Tsirkin
2019-07-29 9:19 ` Paolo Bonzini [this message]
2019-07-30 0:33 ` [virtio-comment] " Huang, Yang
2019-08-03 21:00 ` Michael S. Tsirkin
2019-08-04 2:07 ` [virtio-comment] RE: [virtio-dev] " Huang, Yang
2019-08-04 7:49 ` Michael S. Tsirkin
2019-08-04 13:57 ` Huang, Yang
2019-08-04 18:26 ` Michael S. Tsirkin
2019-08-05 2:39 ` Huang, Yang
2019-08-05 5:57 ` Michael S. Tsirkin
2019-08-05 7:25 ` Huang, Yang
[not found] ` <5B8DA87D05A7694D9FA63FD143655C1B9DC88C3B@hasmsx108.ger.corp.intel.com>
2019-08-05 6:06 ` Michael S. Tsirkin
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=4ecbc7e5-4539-d1f7-eabd-240f5ddd38c5@redhat.com \
--to=pbonzini@redhat.com \
--cc=bing.zhu@intel.com \
--cc=mst@redhat.com \
--cc=tomas.winkler@intel.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=yang.huang@intel.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