|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 06/13] optee: add domain contexts
Hi, On 09/03/2018 05:54 PM, Volodymyr Babchuk wrote: OP-TEE meditor needs to store per-domain context, as will be seen s/meditor/mediator/ in the next patches. At this moment it stores only reference to domain. This allows us to filter out calls from domains that are not allowed to work with OP-TEE. Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx> --- xen/arch/arm/tee/optee.c | 66 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) diff --git a/xen/arch/arm/tee/optee.c b/xen/arch/arm/tee/optee.c index 48bff5d..c895a99 100644 --- a/xen/arch/arm/tee/optee.c +++ b/xen/arch/arm/tee/optee.c @@ -19,6 +19,14 @@ #include <asm/tee/optee_msg.h> #include <asm/tee/optee_smc.h>+struct domain_ctx { I would prefer if the structure has optee in its name such as optee_domain. We also tend to abbreviate context in Xen using the ctxt.
Why do you need to store the context in a list? As you have a context per domain it would be better to store that directly in struct domain by introduce a field "void * tee". With that, most of the code in this patch will become unnecessary. So you potentially can fold it into something else. Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |