public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@nuviainc.com>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: Sami Mujawar <sami.mujawar@arm.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Samer El-Haj-Mahmoud <samer.el-haj-mahmoud@arm.com>,
	Leif Lindholm <leif@nuviainc.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>
Subject: Re: [PATCH 1/1] ArmPkg: Add SMC helper functions
Date: Fri, 22 Oct 2021 10:53:23 -0600	[thread overview]
Message-ID: <cbbec49f-0374-2fb8-918e-64acff000c69@nuviainc.com> (raw)
In-Reply-To: <CAMj1kXFEGwVkstywRt7=M51t8E+woZStMLuu8SwcwRfFdSV52g@mail.gmail.com>

On 10/22/21 9:08 AM, Ard Biesheuvel wrote:
> On Tue, 19 Oct 2021 at 22:35, Rebecca Cran <rebecca@nuviainc.com> wrote:
>> Add functions ArmCallSmc0/1/2/3 to do SMC calls with 0, 1, 2 or 3
>> arguments.
>> The functions return up to 3 values.
>>
> This is a lot of code to do something we already do in our code.
>
> Care to elaborate what the use case is here? In any case, we generally
> try to avoid submitting helper libraries like this without the user,
> to avoid merging code that is already dead.


Sure! With the current interface, there's lots of template code to set 
up the structure and extract results from it. By passing pointers to the 
arguments and results into the functions, this patch removes that 
template code.

I can send out a v2 patch set which includes changes to existing SMC 
calls so the new functions are used.


-- 
Rebecca Cran


      reply	other threads:[~2021-10-22 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 20:35 [PATCH 1/1] ArmPkg: Add SMC helper functions Rebecca Cran
2021-10-22 15:08 ` Ard Biesheuvel
2021-10-22 16:53   ` Rebecca Cran [this message]

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-list 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=cbbec49f-0374-2fb8-918e-64acff000c69@nuviainc.com \
    --to=devel@edk2.groups.io \
    /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