All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: Ilias Apalodimas <apalos@gmail.com>,
	Ying-Chun Liu <paul.liu@linaro.org>,
	Jens Wiklander <jens.wiklander@linaro.org>,
	Alexander Graf <agraf@csgraf.de>,
	U-Boot Mailing List <u-boot@lists.denx.de>
Subject: Re: [PATCH v2] efi_loader: Don't limit the StMM buffer size explicitly
Date: Sat, 25 Dec 2021 21:39:23 +0200	[thread overview]
Message-ID: <Ycdza4LoPTL9DGlC@hades> (raw)
In-Reply-To: <93e7b044-163f-4828-abd9-a9631ecc2ae8@gmx.de>

On Sat, Dec 25, 2021 at 05:13:23PM +0100, Heinrich Schuchardt wrote:
> On 12/25/21 16:04, Ilias Apalodimas wrote:
> > 
> > 
> > On Sat, 25 Dec 2021, 16:28 Heinrich Schuchardt, <xypron.glpk@gmx.de
> > <mailto:xypron.glpk@gmx.de>> wrote:
> > 
> > 
> > 
> >     Am 25. Dezember 2021 12:16:29 MEZ schrieb Ilias Apalodimas
> >     <ilias.apalodimas@linaro.org <mailto:ilias.apalodimas@linaro.org>>:
> >      >> >
> >      >[...]
> >      >> >    rc = tee_invoke_func(conn.tee, &arg, 2, param);
> >      >> >    tee_shm_free(shm);
> >      >> > +  /*
> >      >> > +   * Although the max payload is configurable on StMM, we
> >     only share
> >      >> > +   * four pages from OP-TEE for the non-secure buffer used to
> >     communicate
> >      >> > +   * with StMM. OP-TEE will reject anything bigger than that
> >     and will
> >      >> > +   * return.  So le'ts at least warn users
> >      >> > +   */
> 
> The comment mentioning four pages does not make too much sense to me as
> both OP-TEE as well as U-Boot can be configured to other sizes.
> 

The pages that op-tee uses are not configurable.  What is configurable is
the number of pages you can request op-tee to map from the non-secure
world for u-boot sharing.  However the four page restriction I refer to 
is an internal op-tee one and refers to the non-secure world buffer it 
shares with StandAloneMM, not u-boot [1]

[...]

[1] https://github.com/OP-TEE/optee_os/blob/master/core/arch/arm/kernel/stmm_sp.c#L73
Cheers
/Ilias

  parent reply	other threads:[~2021-12-25 19:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-24  8:08 [PATCH v2] efi_loader: Don't limit the StMM buffer size explicitly Ilias Apalodimas
2021-12-25 10:03 ` Heinrich Schuchardt
2021-12-25 11:16   ` Ilias Apalodimas
2021-12-25 14:28     ` Heinrich Schuchardt
2021-12-25 15:04       ` Ilias Apalodimas
2021-12-25 16:13         ` Heinrich Schuchardt
2021-12-25 19:35           ` Ilias Apalodimas
2021-12-25 19:39           ` Ilias Apalodimas [this message]
2021-12-27  8:26             ` Jens Wiklander
2021-12-27  8:29               ` Ilias Apalodimas
2021-12-27  8:35                 ` Heinrich Schuchardt

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=Ycdza4LoPTL9DGlC@hades \
    --to=ilias.apalodimas@linaro.org \
    --cc=agraf@csgraf.de \
    --cc=apalos@gmail.com \
    --cc=jens.wiklander@linaro.org \
    --cc=paul.liu@linaro.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.