linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jens.wiklander@linaro.org (Jens Wiklander)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 1/5] arm/arm64: add smccc ARCH32
Date: Mon, 14 Sep 2015 10:30:30 +0200	[thread overview]
Message-ID: <20150914083029.GA13963@ermac> (raw)
In-Reply-To: <20150821114331.GA11701@ermac>

On Fri, Aug 21, 2015 at 01:43:31PM +0200, Jens Wiklander wrote:
> On Fri, Aug 21, 2015 at 10:24:30AM +0100, Will Deacon wrote:
> > On Thu, Aug 20, 2015 at 12:37:29PM +0100, Jens Wiklander wrote:
> > > On Wed, Aug 19, 2015 at 05:50:09PM +0100, Will Deacon wrote:
> > > > On Wed, Aug 19, 2015 at 09:40:25AM +0100, Jens Wiklander wrote:
> > > > > Adds helpers to do SMC based on ARM SMC Calling Convention.
> > > > > CONFIG_HAVE_SMCCC is enabled for architectures that may support
> > > > > the SMC instruction. It's the responsibility of the caller to
> > > > > know if the SMC instruction is supported by the platform.
> > > > 
> > > > [...]
> > > > > diff --git a/arch/arm64/kernel/smccc-call.S b/arch/arm64/kernel/smccc-call.S
> > > > > new file mode 100644
> > > > > index 0000000..3ce7fe8
> > > > > --- /dev/null
> > > > > +++ b/arch/arm64/kernel/smccc-call.S
> > > > > @@ -0,0 +1,34 @@
> > > > > +/*
> > > > > + * Copyright (c) 2015, Linaro Limited
> > > > > + *
> > > > > + * This program is free software; you can redistribute it and/or modify
> > > > > + * it under the terms of the GNU General Public License Version 2 as
> > > > > + * published by the Free Software Foundation.
> > > > > + *
> > > > > + * This program is distributed in the hope that it will be useful,
> > > > > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > > > > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> > > > > + * GNU General Public License for more details.
> > > > > + *
> > > > > + */
> > > > > +#include <linux/linkage.h>
> > > > > +
> > > > > +#define SMC_PARAM_W0_OFFS      0
> > > > > +#define SMC_PARAM_W2_OFFS      8
> > > > > +#define SMC_PARAM_W4_OFFS      16
> > > > > +#define SMC_PARAM_W6_OFFS      24
> > > > > +
> > > > > +/* void smccc_call32(struct smccc_param32 *param) */
> > > > > +ENTRY(smccc_call32)
> > > > > +       stp     x28, x30, [sp, #-16]!
> > > > 
> > > > Why are you saving lr?
> > > 
> > > Agree, no point in saving lr, but I still need to decrease sp with 16 to
> > > maintain correct alignment. I'll do it with an str instruction instead.
> > 
> > That or pad out with xzr
> > 
> > > > 
> > > > > +       mov     x28, x0
> > > > > +       ldp     w0, w1, [x28, #SMC_PARAM_W0_OFFS]
> > > > > +       ldp     w2, w3, [x28, #SMC_PARAM_W2_OFFS]
> > > > > +       ldp     w4, w5, [x28, #SMC_PARAM_W4_OFFS]
> > > > > +       ldp     w6, w7, [x28, #SMC_PARAM_W6_OFFS]
> > > > > +       smc     #0
> > > > > +       stp     w0, w1, [x28, #SMC_PARAM_W0_OFFS]
> > > > > +       stp     w2, w3, [x28, #SMC_PARAM_W2_OFFS]
> > > > > +       ldp     x28, x30, [sp], #16
> > > > > +       ret
> > > > > +ENDPROC(smccc_call32)
> > > > 
> > > > Could we deal with this like we do for PSCI instead? (see
> > > > __invoke_psci_fn_smc). We could also then rename psci-call.S to fw-call.S
> > > > and stick this in there too.
> > > 
> > > I assume you're referring to when to use "hvc" and "smc".
> > 
> > No, I mean use a C prototype to avoid marshalling the parameters in assembly
> > like this. As Rutland pointed out, the return value is a bit messy, but
> > the arguments align nicely with the PCS afaict.
> 
> If possible I'd like the function to have the same prototype for both
> arm and arm64. For arm it's not possible to supply more than 4
> parameters. To fully support SMC Calling Convention we need to be able
> to pass 8 parameters and have 4 return values. The OP-TEE driver in this
> patch set depends on this. I don't see how we can avoid the marshalling
> here.
> 
> We could have two versions of the SMCCC functions, one simplified which
> only uses registers and one complete like this one with marshalling.

Will, what do think about this?

Thanks,
Jens

  reply	other threads:[~2015-09-14  8:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  8:40 [PATCH v5 0/5] generic TEE subsystem Jens Wiklander
2015-08-19  8:40 ` [PATCH v5 1/5] arm/arm64: add smccc ARCH32 Jens Wiklander
2015-08-19 10:56   ` Yury
2015-08-20  7:23     ` Jens Wiklander
2015-08-19 16:50   ` Will Deacon
2015-08-20 11:35     ` Michal Simek
2015-08-20 11:37     ` Jens Wiklander
2015-08-20 21:30       ` Mark Rutland
2015-08-21  9:24       ` Will Deacon
2015-08-21 11:43         ` Jens Wiklander
2015-09-14  8:30           ` Jens Wiklander [this message]
2015-09-15 18:26             ` Will Deacon
2015-09-15 21:05               ` Jens Wiklander
2015-09-16 17:18                 ` Will Deacon
2015-08-19  8:40 ` [PATCH v5 2/5] dt/bindings: add bindings for optee Jens Wiklander
2015-09-15 22:37   ` Rob Herring
2015-09-16  7:13     ` Jens Wiklander
2015-08-19  8:40 ` [PATCH v5 3/5] tee: generic TEE subsystem Jens Wiklander
2015-08-19  8:40 ` [PATCH v5 4/5] tee: add OP-TEE driver Jens Wiklander
2015-08-19  8:40 ` [PATCH v5 5/5] Documentation: tee subsystem and op-tee driver Jens Wiklander

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=20150914083029.GA13963@ermac \
    --to=jens.wiklander@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).