From: "NK, JESHWANTHKUMAR" <jeshwanthkumar.nk@amd.com>
To: virtio-comment@lists.oasis-open.org
Cc: Mythri.Pandeshwarakrishna@amd.com, Devaraj.Rangasamy@amd.com,
Rijo-john.Thomas@amd.com, Nimesh.Easow@amd.com,
virtio-dev@lists.oasis-open.org, jens.wiklander@linaro.org,
sumit.semwal@linaro.org, alex.bennee@linaro.org,
arnd.bergmann@linaro.org, op-tee@lists.trustedfirmware.org,
Parav Pandit <parav@nvidia.com>,
Sumit Garg <sumit.garg@linaro.org>
Subject: [virtio-comment] Re: [PATCH v3] virtio-tee: Reserve device ID 46 for TEE device
Date: Thu, 5 Oct 2023 10:40:16 +0530 [thread overview]
Message-ID: <5cf1f33c-73b2-4377-bd5f-242cc18d5762@amd.com> (raw)
In-Reply-To: <cf8eee37bb9f5c2408f0ed8f4798e87b3c01f39c.1695881523.git.JESHWANTHKUMAR.NK@amd.com>
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/175
Request for votes.
Regards,
Jeshwanth
On 28-Sep-23 11:42 AM, jeshwank wrote:
> In a virtual environment, an application running in guest VM may want
> to delegate security sensitive tasks to a Trusted Application (TA)
> running within a Trusted Execution Environment (TEE). A TEE is a trusted
> OS running in some secure environment, for example, TrustZone on ARM
> CPUs, or a separate secure co-processor etc.
>
> A virtual TEE device emulates a TEE within a guest VM. Such a virtual
> TEE device supports multiple operations such as:
>
> VIRTIO_TEE_CMD_OPEN_DEVICE – Open a communication channel with virtio
> TEE device.
> VIRTIO_TEE_CMD_CLOSE_DEVICE – Close communication channel with virtio
> TEE device.
> VIRTIO_TEE_CMD_GET_VERSION – Get version of virtio TEE.
> VIRTIO_TEE_CMD_OPEN_SESSION – Open a session to communicate with
> trusted application running in TEE.
> VIRTIO_TEE_CMD_CLOSE_SESSION – Close a session to end communication
> with trusted application running in TEE.
> VIRTIO_TEE_CMD_INVOKE_FUNC – Invoke a command or function in trusted
> application running in TEE.
> VIRTIO_TEE_CMD_CANCEL_REQ – Cancel an ongoing command within TEE.
> VIRTIO_TEE_CMD_REGISTER_MEM - Register shared memory with TEE.
> VIRTIO_TEE_CMD_UNREGISTER_MEM - Unregister shared memory from TEE.
>
> We would like to reserve device ID 46 for Virtio-TEE device.
>
> Signed-off-by: Jeshwanth Kumar <jeshwanthkumar.nk@amd.com>
> Reviewed-by: Rijo Thomas <Rijo-john.Thomas@amd.com>
> Reviewed-by: Parav Pandit <parav@nvidia.com>
> Acked-by: Sumit Garg <sumit.garg@linaro.org>
> ---
> content.tex | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 0a62dce..644aa4a 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -739,6 +739,8 @@ \chapter{Device Types}\label{sec:Device Types}
> \hline
> 45 & SPI master \\
> \hline
> +46 & TEE device \\
> +\hline
> \end{tabular}
>
> Some of the devices above are unspecified by this document,
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/
prev parent reply other threads:[~2023-10-05 5:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 6:12 [virtio-comment] [PATCH v3] virtio-tee: Reserve device ID 46 for TEE device jeshwank
2023-10-05 5:10 ` NK, JESHWANTHKUMAR [this message]
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=5cf1f33c-73b2-4377-bd5f-242cc18d5762@amd.com \
--to=jeshwanthkumar.nk@amd.com \
--cc=Devaraj.Rangasamy@amd.com \
--cc=Mythri.Pandeshwarakrishna@amd.com \
--cc=Nimesh.Easow@amd.com \
--cc=Rijo-john.Thomas@amd.com \
--cc=alex.bennee@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=parav@nvidia.com \
--cc=sumit.garg@linaro.org \
--cc=sumit.semwal@linaro.org \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.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 read-only IMAP folder(s) and NNTP newsgroup(s).