From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Supreeth Venkatesh <supreeth.venkatesh@arm.com>
Cc: Achin Gupta <achin.gupta@arm.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
nd@arm.com
Subject: Re: [PATCH 1/1] ArmPkg/Include: Add standard SMC and SVC function IDs for MM interface.
Date: Fri, 22 Sep 2017 15:15:33 -0700 [thread overview]
Message-ID: <CAKv+Gu91w_0o-_m57wnqq0OLRGmqPGAPuSkakWtJPNy23o+0JA@mail.gmail.com> (raw)
In-Reply-To: <1506118336.2623.5.camel@arm.com>
On 22 September 2017 at 15:12, Supreeth Venkatesh
<supreeth.venkatesh@arm.com> wrote:
> On Fri, 2017-09-22 at 22:45 +0100, Achin Gupta wrote:
>> Hi Supreeth,
>>
>> On Fri, Sep 22, 2017 at 08:25:39PM +0100, Supreeth Venkatesh wrote:
>> >
>> > This patch adds a list of function IDs that fall under the standard
>> > SMC range as defined in
>> > http://infocenter.arm.com/help/topic/com.arm.doc.den0060a/DEN0060A_
>> > ARM_MM_Interface_Specification.pdf.
>> >
>> > SMCs associated with Management Mode are in the range 0xC4000040 -
>> > 0xC400005f (64 bit) and 0x84000040 - 0x8400005f (32 bit).
>> >
>> > The function(s) available to the normal world:
>> > 1. Request services from the secure MM environment using
>> > MM_COMMUNICATE.
>> >
>> > SVCs are in the range 0xC4000060 - 0xC400007f.
>> > The functions available to the secure MM partition:
>> > 1. Signal completion of MM event handling.
>> > 2. Set/Get memory attributes for a memory region at runtime.
>> > 3. Get version number of secure partition manager.
>> >
>> > Also, it defines memory attributes and MM return codes.
>> The SVCs in the 0xC4000060 - 0xC400007f range are not a part of the
>> MM interface
>> specification. At the moment, these are used to implement an
>> interface between
>> ARM TF in EL3 and S-EL0. These should go into a separate patch that
>> introduces
>> them as an ARM TF ABI.
>>
>> cheers,
>> Achin
>
> Thanks for taking a look at it. This was added in ArmStdSmc.h
> deliberately to request comments/feedback. I don't think SVC defines
> belong in this file at all. It should have its own header file.
>
> Since it is specific to MM (S-EL0) - EL3 communication, I am tempted to
> create a new header file named "ArmMmSvc.h" and put in
> ArmPkg/Include/IndustryStandard folder.
>
> Comments - Maintainers/Anyone?
If these are only used for SVC calls from S-EL0, then yes, they should
be in a separate header file.
prev parent reply other threads:[~2017-09-22 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 19:25 [PATCH 1/1] ArmPkg/Include: Add standard SMC and SVC function IDs for MM interface Supreeth Venkatesh
2017-09-22 21:45 ` Achin Gupta
2017-09-22 22:12 ` Supreeth Venkatesh
2017-09-22 22:15 ` Ard Biesheuvel [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=CAKv+Gu91w_0o-_m57wnqq0OLRGmqPGAPuSkakWtJPNy23o+0JA@mail.gmail.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