[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] arm: dom0less: add TEE support
- To: Julien Grall <julien@xxxxxxx>
- From: Bertrand Marquis <Bertrand.Marquis@xxxxxxx>
- Date: Thu, 30 May 2024 13:22:50 +0000
- Accept-language: en-GB, en-US
- Arc-authentication-results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 63.35.35.123) smtp.rcpttodomain=lists.xenproject.org smtp.mailfrom=arm.com; dmarc=pass (p=none sp=none pct=100) action=none header.from=arm.com; dkim=pass (signature was verified) header.d=arm.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=arm.com] dkim=[1,1,header.d=arm.com] dmarc=[1,1,header.from=arm.com])
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
- Arc-message-signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=xvybumCqWgkYIZD6Th8cbehhH1VZ5yOfQbP5Ck7p3bU=; b=FkmpZ7iv/YO9eZiItsRKl9FhoR9nFpgY6D5esr8SZN8qMn++KinGADW8ooSxeHWkeYuQOsWF/d89VTd9TvlerNcxzcNlO4psXTsaqV3IhL2o3wiyxulvBH9L7bxkHncd6NvH0MjSEmltKnZ3F6ojBy1p20mCJQe4hffACF+M8ptjeCeWXBV6N5gFd1NA4CyXc7r5319xQqrjU8aifSeSb/8ktIdP8/lQVwXhc9/zuzQuT1bf/Qv/OqpqIOfdzQKgIEovunKKc0Udr4XD39W57FIX48aNFTlA9fuZD+zxQ8uDRlzfsO0flv07VzR3tvnDwMcwWuRMHzCtDFvc5pkH1w==
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=xvybumCqWgkYIZD6Th8cbehhH1VZ5yOfQbP5Ck7p3bU=; b=JxG/rt/x+ucDP4QVGeHMwCdBWEiqxsx2VethMvl2rL9/NaEUn/tjSPKaH8s7LYyZjZenrqPqDucyTngHtKC2xta0IZtl9vv1EjfTRMaHSPFSiBDRostRXsRm9CkiqinmoOYsx1dw01TS6/YASNuLfVx8OxP5PELp/0ZVd6EkAvcejrRg6Zn02Q0s2VLhhHRfBJ1QyJpnuTCGQSlh1MJszDp9786QbdrNqDnicsBoUwDDV7hArDx243toCsU+CltuI99dSntoIuCuoyI0PrwC4vsYhJ4cE01+7OA9XxSW7B67LfkZZN1dGFAhGObQxzVCGLazwHelPtH0+Rc0du1Giw==
- Arc-seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=TowmUU8xO316RJ7dL9LKEFjVUnBj7gTIOJRV/JwDmGzBU9cwN+jJHFJtYASYfoXIQPMP/pn6ZnNcwIimyLmsiMLa3tLg1YtryjXjRXXOahkMffeQWd6H+UJD3MMHT4BPvcgugo4ksq7a4L8T9BpcWqOWoyHPt5qkuYpVDcl8H7Au6o2YMftwKEnbZfAZDONqCzcsb19UfL/E+DIeUVNUNkmwp72/Pl8hCwt+Zsc7XVqd2qm40zNO+T4ZrVficooYu+I0LxiIzPRqfGT9MWInGiPrLrLhX1rLHIbP8kquDsfPGX0FJbxKJydJ+uV7XBeWq21dvbwOmXbhw/htx86n/g==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UNVsBOsGqqIia0frtU04RjPQDJJTjqpZDVqfiI01idOnN/1KO0BC4C6oeMxVXEHIDn+Ext/aDCsN0WIpZG+PTmhvxknRs0uMlAfFuz1qbkCoYUEmB/ksMJfDW8gDn0yFbSxOGVpEGZlzs2/iQun1iOvQzuEg5nkNVkFAdKf3qfC73E7/NkyXdOTxeCnRg8AeCR60vvuD3P6OX+bvvvWdxxvUCisSBKkrdD2Q+UhxPNVsgUG9oMUItO4lShMGRqhuFdimbllktAoMwBCifle9S5iTHDuLaLcafA7AL8zu+ea9QFo82X5zEcy9HVBRgGZSxCxJEJJhCKxc0Lw714x/5g==
- Authentication-results-original: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Cc: Volodymyr Babchuk <Volodymyr_Babchuk@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Michal Orzel <michal.orzel@xxxxxxx>
- Delivery-date: Thu, 30 May 2024 13:23:13 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
- Nodisclaimer: true
- Original-authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=arm.com;
- Thread-index: AQHasgjZKwS4pdCyJUe9LewXYMLHeLGutaSAgAAAkICAANCCAIAAD1cAgAAuxIA=
- Thread-topic: [PATCH] arm: dom0less: add TEE support
Hi Julien,
> On 30 May 2024, at 12:35, Julien Grall <julien@xxxxxxx> wrote:
>
> Hi Bertrand,
>
> On 30/05/2024 10:40, Bertrand Marquis wrote:
>>> But we are making assumption that all TEE implementation will have its
>>> node inside "/firmware/". I am not 100% sure that this is correct. For
>>> example I saw that Google Trusty uses "/trusty" node (directly inside
>>> the DTS root). On other hand, it is not defined in dts bindings, as far
>>> as I know.
>> Regarding the firmware part you can easily handle that by looking for
>> /firmware
>> and create it if it does not exist before creating your sub-node and this
>> should
>> be node in the optee node creation function not in tee.c.
>
> This would work if the node /firmware doesn't exist. But how would you handle
> the case where it is already present?
>
> I looked at the libfdt API and AFAICT the DTB creation needs to be linear.
> IOW, you can't add a subnode to an already created node.
>
> There is an helper to create a placeholder, but AFAIK this is only for a
> property. You also need to know the size in advance.
I thought it was possible but i definitely can be wrong.
As right now we have only one need for the node, we could delay a possible
solution and just create it in the optee driver.
Designing a solution for a possible future case right now seems a bit complex
without a use case.
Cheers
Bertrand
>
> Cheers,
>
> --
> Julien Grall
|