From: "NK, JESHWANTHKUMAR" <jeshwanthkumar.nk@amd.com>
To: Parav Pandit <parav@nvidia.com>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>
Cc: "Mythri.Pandeshwarakrishna@amd.com"
<Mythri.Pandeshwarakrishna@amd.com>,
"Devaraj.Rangasamy@amd.com" <Devaraj.Rangasamy@amd.com>,
"Rijo-john.Thomas@amd.com" <Rijo-john.Thomas@amd.com>,
"Nimesh.Easow@amd.com" <Nimesh.Easow@amd.com>,
"babulu.ellune@amd.com" <babulu.ellune@amd.com>
Subject: Re: [virtio-dev] [PATCH] virtio-tee: Reserve device ID 46 for TEE device
Date: Thu, 21 Sep 2023 15:41:08 +0530 [thread overview]
Message-ID: <7cf06aec-5787-423a-876e-cd5fb581c225@amd.com> (raw)
In-Reply-To: <PH0PR12MB54810E429F2FE6E18E4D5987DCF9A@PH0PR12MB5481.namprd12.prod.outlook.com>
On 20-Sep-23 3:15 PM, Parav Pandit wrote:
> Hi,
>
>> From: virtio-dev@lists.oasis-open.org <virtio-dev@lists.oasis-open.org> On
>> Behalf Of jeshwank
>> Sent: Wednesday, September 6, 2023 3:13 PM
>>
>> The virtio-tee device allows guest OS to access the TEE present in host system,
>> to perform secure operations.
>>
>> This patch is to reserve a device ID 46 for virtio-tee device.
>>
> For those who breath TEE its may be obvious thing. 😊
> For me, a humble request,
> can you please expand this patch to contain short description of basic functionality of the TEE device to encompass under this device-id?
Ack, will post a new patch addressing this.
>
>> Signed-off-by: jeshwank <JESHWANTHKUMAR.NK@amd.com>
>> ---
>> 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,
>> --
>> 2.25.1
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
prev parent reply other threads:[~2023-09-21 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 9:42 [virtio-dev] [PATCH] virtio-tee: Reserve device ID 46 for TEE device jeshwank
2023-09-20 9:45 ` Parav Pandit
2023-09-21 10:11 ` 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=7cf06aec-5787-423a-876e-cd5fb581c225@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=babulu.ellune@amd.com \
--cc=parav@nvidia.com \
--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