linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Rijo Thomas <Rijo-john.Thomas@amd.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
	Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>,
	Mythri Pandeshwara krishna <mythri.pandeshwarakrishna@amd.com>,
	OP-TEE TrustedFirmware <op-tee@lists.trustedfirmware.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] tee: amdtee: unload TA only when its refcount becomes 0
Date: Wed, 5 May 2021 13:09:17 +0200	[thread overview]
Message-ID: <CAHUa44HSaFYHUNEJ9S13czP5EZd2NdpWqaQN6zXaAn0ekt88Ag@mail.gmail.com> (raw)
In-Reply-To: <01387b92-263c-edf1-52bf-b2244ebbd311@amd.com>

On Tue, May 4, 2021 at 6:26 AM Rijo Thomas <Rijo-john.Thomas@amd.com> wrote:
>
>
>
> On 03/05/21 5:17 pm, Dan Carpenter wrote:
> > On Mon, May 03, 2021 at 09:04:35AM +0530, Rijo Thomas wrote:
> >>
> >>
> >> On 14/04/21 11:08 pm, Rijo Thomas wrote:
> >>> Same Trusted Application (TA) can be loaded in multiple TEE contexts.
> >>>
> >>> If it is a single instance TA, the TA should not get unloaded from AMD
> >>> Secure Processor, while it is still in use in another TEE context.
> >>>
> >>> Therefore reference count TA and unload it when the count becomes zero.
> >>>
> >>> Fixes: 757cc3e9ff1d ("tee: add AMD-TEE driver")
> >>> Reviewed-by: Devaraj Rangasamy <Devaraj.Rangasamy@amd.com>
> >>> Signed-off-by: Rijo Thomas <Rijo-john.Thomas@amd.com>
> >>
> >> Hi Dan,
> >>
> >> Can you please give an Ack if you are okay with this patch.
> >> I have incorporated your review comments for v2.
> >>
> >
> > Oh, Sorry.  Thanks!
> >
> > Acked-by: Dan Carpenter <dan.carpenter@oracle.com>
>
> Thanks Dan!
>
> Jens, can you please pull in this patch.

Done!

Cheers,
Jens

      reply	other threads:[~2021-05-05 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-14 17:38 [PATCH v3] tee: amdtee: unload TA only when its refcount becomes 0 Rijo Thomas
2021-05-03  3:34 ` Rijo Thomas
2021-05-03 11:47   ` Dan Carpenter
2021-05-04  4:26     ` Rijo Thomas
2021-05-05 11:09       ` Jens Wiklander [this message]

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=CAHUa44HSaFYHUNEJ9S13czP5EZd2NdpWqaQN6zXaAn0ekt88Ag@mail.gmail.com \
    --to=jens.wiklander@linaro.org \
    --cc=Devaraj.Rangasamy@amd.com \
    --cc=Rijo-john.Thomas@amd.com \
    --cc=dan.carpenter@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mythri.pandeshwarakrishna@amd.com \
    --cc=op-tee@lists.trustedfirmware.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).