From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Jens Wiklander <jens.wiklander@linaro.org>
Cc: OP-TEE TrustedFirmware <op-tee@lists.trustedfirmware.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 1/1] tee: optee: Provide special parameter field for UUID values
Date: Mon, 19 Apr 2021 15:01:32 +0300 [thread overview]
Message-ID: <YH1xHDbFyJ1URYYV@smile.fi.intel.com> (raw)
In-Reply-To: <CAHUa44FWJiL1yzHR0jwL2VJG_4t_O6An48v47gORitcaahwmYw@mail.gmail.com>
On Mon, Apr 19, 2021 at 01:35:51PM +0200, Jens Wiklander wrote:
> On Thu, Apr 15, 2021 at 4:58 PM Andy Shevchenko
> <andriy.shevchenko@linux.intel.com> wrote:
Thanks for review, my answer below.
> > struct optee_msg_param_tmem tmem;
> > struct optee_msg_param_rmem rmem;
> > struct optee_msg_param_value value;
> > + uuid_t uuid;
>
> It's nice to get rid of the cast above, but I'm not that keen on the
> change in this struct. This file defines the ABI towards Secure world
> and adding dependencies on external complex types is a larger problem
> than the cast above in my opinion.
I understand.
So, the cast is simply wrong there. Can you add a comment above that cast to
explain that and make it is marked as FIXME? Because there is no guarantee that
internal Linux types can be 1:1 mapped to the ABI of something.
What you need, perhaps, is a middle layer function that will copy u64 data
to uuid_t or so. Also, u64 is not an ABI type, why the respective __uXX
variants are not in use?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-04-19 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 14:58 Andy Shevchenko
2021-04-19 11:35 ` Jens Wiklander
2021-04-19 12:01 ` Andy Shevchenko [this message]
2021-04-19 13:19 ` Jens Wiklander
2021-04-19 13:40 ` Andy Shevchenko
2021-04-19 14:30 ` Jens Wiklander
2021-04-19 14:41 ` Andy Shevchenko
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=YH1xHDbFyJ1URYYV@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=jens.wiklander@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®