Re: [Xen-devel] [PATCH v2 07/13] optee: add std call handling

[Julien Grall <julien.grall@xxxxxxx>]

On 11/09/18 12:31, Volodymyr Babchuk wrote:
> On 11.09.18 14:19, Julien Grall wrote:
> > On 10/09/18 18:37, Volodymyr Babchuk wrote:
> > > Hi Julien,
> > Hi,
> >
> > > On 05.09.18 18:17, Julien Grall wrote:
> > > > Hi,
> > > >
> > > > On 09/03/2018 05:54 PM, Volodymyr Babchuk wrote:
> > > > > Main way to communicate with OP-TEE is to issue standard SMCCC
> > > > NIT: The main way
> > > >
> > > > > call. "Standard" is a SMCCC term and it means that call can be
> > > > > interrupted and OP-TEE can return control to NW before completing
> > > > > the call.
> > > > >
> > > > > In contranst with fast calls, where arguments and return values
> > > > NIT: s/contranst/contrast/
> > > >
> > > > > are passed in registers, standard calls use shared memory. Register
> > > > > pair r1,r2 holds 64-bit PA of command buffer, where all arguments
> > > > Do you mean w1, w2?
> > > Good question. How to call the registers, so it would be valid both
> > > for ARMv7 and ARMv8?
> > Which naming does OP-TEE use? Is it a*?
> Exactly. I've seen the same convention in XEN, in smccc code. So, a*, then?
It would be nice to stay consistent with OP-TEE. So I think a* suits better.

Cheers,

--
Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel