From: Sumit Garg <sumit.garg@linaro.org>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
OP-TEE TrustedFirmware <op-tee@lists.trustedfirmware.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Marc Bonnici <marc.bonnici@arm.com>,
Jerome Forissier <jerome@forissier.org>,
Sughosh Ganu <sughosh.ganu@linaro.org>
Subject: Re: [PATCH v3 1/5] tee: add sec_world_id to struct tee_shm
Date: Wed, 28 Jul 2021 14:11:37 +0530 [thread overview]
Message-ID: <CAFA6WYPW3XQiXJSxsj_HDXZ_JPEx58hOZiZ1Yctn-r7FG6hUpg@mail.gmail.com> (raw)
In-Reply-To: <20210722121757.1944658-2-jens.wiklander@linaro.org>
On Thu, 22 Jul 2021 at 17:48, Jens Wiklander <jens.wiklander@linaro.org> wrote:
>
> Adds sec_world_id to struct tee_shm which describes a shared memory
> object. sec_world_id can be used by a driver to store an id assigned by
> secure world.
>
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
> ---
> include/linux/tee_drv.h | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
Reviewed-by: Sumit Garg <sumit.garg@linaro.org>
-Sumit
> diff --git a/include/linux/tee_drv.h b/include/linux/tee_drv.h
> index 54269e47ac9a..1a29f0e66e13 100644
> --- a/include/linux/tee_drv.h
> +++ b/include/linux/tee_drv.h
> @@ -196,7 +196,11 @@ int tee_session_calc_client_uuid(uuid_t *uuid, u32 connection_method,
> * @num_pages: number of locked pages
> * @dmabuf: dmabuf used to for exporting to user space
> * @flags: defined by TEE_SHM_* in tee_drv.h
> - * @id: unique id of a shared memory object on this device
> + * @id: unique id of a shared memory object on this device, shared
> + * with user space
> + * @sec_world_id:
> + * secure world assigned id of this shared memory object, not
> + * used by all drivers
> *
> * This pool is only supposed to be accessed directly from the TEE
> * subsystem and from drivers that implements their own shm pool manager.
> @@ -212,6 +216,7 @@ struct tee_shm {
> struct dma_buf *dmabuf;
> u32 flags;
> int id;
> + u64 sec_world_id;
> };
>
> /**
> --
> 2.31.1
>
next prev parent reply other threads:[~2021-07-28 8:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 12:17 [PATCH v3 0/5] Add FF-A support in OP-TEE driver Jens Wiklander
2021-07-22 12:17 ` [PATCH v3 1/5] tee: add sec_world_id to struct tee_shm Jens Wiklander
2021-07-28 8:41 ` Sumit Garg [this message]
2021-07-22 12:17 ` [PATCH v3 2/5] optee: simplify optee_release() Jens Wiklander
2021-07-28 8:45 ` Sumit Garg
2021-07-29 6:43 ` Jens Wiklander
2021-07-29 7:10 ` Sumit Garg
2021-07-22 12:17 ` [PATCH v3 3/5] optee: refactor driver with internal callbacks Jens Wiklander
2021-07-28 9:59 ` Sumit Garg
2021-07-29 6:56 ` Jens Wiklander
2021-07-29 7:15 ` Sumit Garg
2021-07-22 12:17 ` [PATCH v3 4/5] optee: isolate smc abi Jens Wiklander
2021-07-28 10:10 ` Sumit Garg
2021-07-29 7:10 ` Jens Wiklander
2021-07-22 12:17 ` [PATCH v3 5/5] optee: add FF-A support Jens Wiklander
2021-07-26 10:29 ` [PATCH v3 0/5] Add FF-A support in OP-TEE driver Sumit Garg
2021-07-26 10:54 ` Sudeep Holla
2021-07-26 11:41 ` Sumit Garg
2021-07-26 15:25 ` Jens Wiklander
2021-07-27 6:13 ` Sumit Garg
2021-07-28 6:40 ` Jens Wiklander
2021-07-28 10:22 ` Sumit Garg
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=CAFA6WYPW3XQiXJSxsj_HDXZ_JPEx58hOZiZ1Yctn-r7FG6hUpg@mail.gmail.com \
--to=sumit.garg@linaro.org \
--cc=jens.wiklander@linaro.org \
--cc=jerome@forissier.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.bonnici@arm.com \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sudeep.holla@arm.com \
--cc=sughosh.ganu@linaro.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 NNTP newsgroup(s).