From: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com>
To: Harshal Dev <harshal.dev@oss.qualcomm.com>,
Jens Wiklander <jens.wiklander@oss.qualcomm.com>,
Sumit Garg <sumit.garg@kernel.org>,
Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: Basant Kumar <basantk@qti.qualcomm.com>,
Apurupa Pattapu <apurupa@qti.qualcomm.com>,
Arun Kumar Neelakantam <aneelaka@qti.qualcomm.com>,
op-tee@lists.trustedfirmware.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Sumit Garg <sumit.garg@oss.qualcomm.com>
Subject: Re: [PATCH v5 1/7] tee: qcomtee: Track the object invocation context
Date: Fri, 16 Oct 2026 18:23:55 +0530 [thread overview]
Message-ID: <edaa8679-63a6-45b8-9e36-c04740f20332@oss.qualcomm.com> (raw)
In-Reply-To: <20261015-qcom_uefisecapp_migrate_qcomtee-v5-1-1460691b35d3@oss.qualcomm.com>
On 15-10-2026 17:09, Harshal Dev wrote:
> QCOMTEE needs to distinguish between object invocations arriving from
> kernel clients and user-space clients in order to correctly marshal
> UBUF parameters and decide whether certain operations should be permitted.
>
> Introduce an enum tee_object_invoke_origin to allow clients to indicate
> the context of the TEE object invocation, and add a kernel_ctx flag to the
> QCOMTEE context so the TEE back-end can track it.
>
> Reviewed-by: Sumit Garg <sumit.garg@oss.qualcomm.com>
> Reviewed-by: Amirreza Zarrabi <amirreza.zarrabi@oss.qualcomm.com>
> Signed-off-by: Harshal Dev <harshal.dev@oss.qualcomm.com>
Tested-by: Kuldeep Singh <kuldeep.singh@oss.qualcomm.com> #on Glymur-crd
--
Regards
Kuldeep
next prev parent reply other threads:[~2026-10-16 12:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 11:39 [PATCH v5 0/7] Add TEE based client driver for UEFI Secure Application Harshal Dev
2026-10-15 11:39 ` [PATCH v5 1/7] tee: qcomtee: Track the object invocation context Harshal Dev
2026-10-16 12:53 ` Kuldeep Singh [this message]
2026-10-15 11:39 ` [PATCH v5 2/7] tee: Add kernel client object invoke helper Harshal Dev
2026-10-16 12:54 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 3/7] tee: qcomtee: Allow object invokes from kernel clients Harshal Dev
2026-10-16 12:55 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 4/7] tee: Export uuidv5 generation for TEE backends Harshal Dev
2026-10-16 12:55 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 5/7] tee: qcomtee: Add support for registering QTEE services on TEE bus Harshal Dev
2026-10-16 12:56 ` Kuldeep Singh
2026-10-15 11:39 ` [PATCH v5 6/7] firmware: qcom: Add support for TEE based EFI-var client driver Harshal Dev
2026-10-15 11:39 ` [PATCH v5 7/7] arm64: defconfig: Enable UefiSecApp TEE client driver for Qualcomm SoCs Harshal Dev
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=edaa8679-63a6-45b8-9e36-c04740f20332@oss.qualcomm.com \
--to=kuldeep.singh@oss.qualcomm.com \
--cc=amirreza.zarrabi@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=aneelaka@qti.qualcomm.com \
--cc=apurupa@qti.qualcomm.com \
--cc=basantk@qti.qualcomm.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=harshal.dev@oss.qualcomm.com \
--cc=jens.wiklander@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@kernel.org \
--cc=sumit.garg@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®