public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	op-tee@lists.trustedfirmware.org
Subject: [GIT PULL] OP-TEE kernel private shared memory optimizations for 6.8
Date: Mon, 11 Dec 2023 12:58:15 +0100	[thread overview]
Message-ID: <20231211115815.GA616539@rayden> (raw)

Hello arm-soc maintainers,

Please pull these two patches that optmize how the OP-TEE driver private
shared memory allocated as dynamic shared memory.

Thanks,
Jens

The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

  https://git.linaro.org/people/jens.wiklander/linux-tee.git tags/kern-priv-shm-for-v6.8

for you to fetch changes up to 225a36b96359aceaa9a6399f2dff99627397e637:

  optee: allocate shared memory with alloc_pages_exact() (2023-12-04 14:48:42 +0100)

----------------------------------------------------------------
OP-TEE kernel private shared memory optimizations

Optimize OP-TEE driver private shared memory allocated as dynamic shared
memory. Both to handle larger than one page allocations and for more
efficient memory usage.

----------------------------------------------------------------
Jens Wiklander (2):
      optee: add page list to kernel private shared memory
      optee: allocate shared memory with alloc_pages_exact()

 drivers/tee/optee/core.c    | 44 +++++++++++++++++++++++---------------------
 drivers/tee/optee/smc_abi.c | 45 +++++++++++++++++++++------------------------
 2 files changed, 44 insertions(+), 45 deletions(-)

                 reply	other threads:[~2023-12-11 11:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20231211115815.GA616539@rayden \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=soc@kernel.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