From: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
To: "Konrad Dybcio" <konrad.dybcio@oss.qualcomm.com>,
"Jens Wiklander" <jens.wiklander@linaro.org>,
"Sumit Garg" <sumit.garg@kernel.org>,
"Bjorn Andersson" <andersson@kernel.org>,
"Konrad Dybcio" <konradybcio@kernel.org>,
"Bartosz Golaszewski" <bartosz.golaszewski@linaro.org>,
"Apurupa Pattapu" <quic_apurupa@quicinc.com>,
"Kees Cook" <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Sumit Semwal" <sumit.semwal@linaro.org>,
"Christian König" <christian.koenig@amd.com>
Cc: Harshal Dev <quic_hdev@quicinc.com>,
linux-arm-msm@vger.kernel.org, op-tee@lists.trustedfirmware.org,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
linux-doc@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v7 07/11] firmware: qcom: tzmem: export shm_bridge create/delete
Date: Thu, 14 Aug 2025 07:47:14 +1000 [thread overview]
Message-ID: <0af9ac59-9b91-4a0b-92fb-b44e0e008431@oss.qualcomm.com> (raw)
In-Reply-To: <f10f1602-972a-491f-9c11-95e5e7bd80f8@oss.qualcomm.com>
On 8/13/2025 8:06 PM, Konrad Dybcio wrote:
> On 8/13/25 2:35 AM, Amirreza Zarrabi wrote:
>> Anyone with access to contiguous physical memory should be able to
>> share memory with QTEE using shm_bridge.
>>
>> Tested-by: Neil Armstrong <neil.armstrong@linaro.org>
>> Tested-by: Harshal Dev <quic_hdev@quicinc.com>
>> Signed-off-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
>> ---
>
> Hm, I thought the idea for the tzmem allocator was to abstract
> these operations to prevent users from shooting themselves in
> the foot, and this seems to be circumventing that..
>
Yes and no. The TEE subsystem has its own memory management code, and
the qcomtee backed driver will utilize it. In other words, qcomtee will
manage its own memory, and tzmem will only be used for drivers that
communicate with QTEE without involving the TEE subsystem.
This aligns with future extensions for FFA memory sharing.
Regards,
Amir
> Konrad
next prev parent reply other threads:[~2025-08-13 21:47 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 0:35 [PATCH v7 00/11] Trusted Execution Environment (TEE) driver for Qualcomm TEE (QTEE) Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 01/11] tee: allow a driver to allocate a tee_device without a pool Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 02/11] tee: add close_context to TEE driver operation Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 03/11] tee: add TEE_IOCTL_PARAM_ATTR_TYPE_UBUF Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 04/11] tee: add TEE_IOCTL_PARAM_ATTR_TYPE_OBJREF Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 05/11] tee: increase TEE_MAX_ARG_SIZE to 4096 Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 06/11] firmware: qcom: scm: add support for object invocation Amirreza Zarrabi
2025-08-13 9:53 ` Konrad Dybcio
2025-08-13 21:37 ` Amirreza Zarrabi
2025-08-13 22:52 ` Konrad Dybcio
2025-08-13 22:55 ` Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 07/11] firmware: qcom: tzmem: export shm_bridge create/delete Amirreza Zarrabi
2025-08-13 10:06 ` Konrad Dybcio
2025-08-13 21:47 ` Amirreza Zarrabi [this message]
2025-08-13 10:11 ` Kuldeep Singh
2025-08-13 0:35 ` [PATCH v7 08/11] tee: add Qualcomm TEE driver Amirreza Zarrabi
2025-08-13 21:28 ` kernel test robot
2025-08-13 0:35 ` [PATCH v7 09/11] qcomtee: add primordial object Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 10/11] qcomtee: enable TEE_IOC_SHM_ALLOC ioctl Amirreza Zarrabi
2025-08-13 10:00 ` Konrad Dybcio
2025-08-13 22:24 ` Amirreza Zarrabi
2025-08-13 22:49 ` Konrad Dybcio
2025-08-13 23:07 ` Amirreza Zarrabi
2025-08-13 23:19 ` Amirreza Zarrabi
2025-08-13 23:20 ` Konrad Dybcio
2025-08-13 23:23 ` Amirreza Zarrabi
2025-08-14 5:50 ` Amirreza Zarrabi
2025-08-13 0:35 ` [PATCH v7 11/11] Documentation: tee: Add Qualcomm TEE driver Amirreza Zarrabi
2025-08-13 7:49 ` [PATCH v7 00/11] Trusted Execution Environment (TEE) driver for Qualcomm TEE (QTEE) Jens Wiklander
2025-08-13 21:39 ` Amirreza Zarrabi
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=0af9ac59-9b91-4a0b-92fb-b44e0e008431@oss.qualcomm.com \
--to=amirreza.zarrabi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=bartosz.golaszewski@linaro.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavoars@kernel.org \
--cc=jens.wiklander@linaro.org \
--cc=kees@kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=quic_apurupa@quicinc.com \
--cc=quic_hdev@quicinc.com \
--cc=sumit.garg@kernel.org \
--cc=sumit.semwal@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).