From: Sughosh Ganu <sughosh.ganu@arm.com>
To: Achin Gupta <Achin.Gupta@arm.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
nd <nd@arm.com>, "jiewen.yao@intel.com" <jiewen.yao@intel.com>
Subject: Re: [PATCH v2 0/2] StandaloneMM: Update permissions for Standalone MM drivers memory area
Date: Sat, 1 Dec 2018 09:56:52 +0530 [thread overview]
Message-ID: <20181201042652.GA29905@arm.com> (raw)
In-Reply-To: <20181130233851.GS4897@e104320-lin>
hi Achin,
On Sat Dec 01, 2018 at 05:08:50AM +0530, Achin Gupta wrote:
> Hi Sughosh,
>
> +Jiewen
>
> I took the patches for a spin and it looks like the FVP port is broken. Some
> reasons are:
>
> 1. The build breaks due to a reference to ArmMmuLib in StandaloneMmPkg.dsc
> 2. There is a broken dependency on PL011UartClockLib in StandaloneMmPkg.dsc
> 3. GCC flags to enforce strict alignment and no fp are required in
> StandaloneMmPkg.dsc to avoid a runtime fault
> 4. There is a data structre in StandaloneMmCoreEntryPoint.c that needs to be
> memzeroed due to the alignment checks
>
> Even after these fixes, I am unable to boot the MM SP. The SP boots with the
> previous revision of your patches and the above fixes. Something has broken
> between the two. I am suspecting the MMU library for S-EL0.
I had tested the patches which i had sent out for ArmPkg changes with
the error handling and error reporting feature on sgi575 before
posting the patches. In addition to the changes that you mention, i
was required to make a couple of more changes in the StandadloneMm
description file.
1) StandaloneMmMmuLib|ArmPkg/Library/StandaloneMmMmuLib/ArmMmuStandaloneMmLib.inf
This was changed from ArmMmuLib which was used earlier.
2) PeCoffExtraActionLib|StandaloneMmPkg/Library/StandaloneMmPeCoffExtraActionLib/StandaloneMmPeCoffExtraActionLib.inf
I had changed this to reflect the change made in the patch
StandaloneMM: Update permissions for Standalone MM drivers memory area
Can you please confirm that you tested with these two additional
changes made. Meanwhile, I will incorporate your review comments which
you make below. Thanks.
-sughosh
>
> Lets sort this out first. Apart from this, could you move this library into
> an AArch64 directory as is the case for other Arm specific libraries
> e.g. StandaloneMmCoreEntryPoint/AArch64
>
> cheers,
> Achin
>
> On Tue, Nov 27, 2018 at 11:52:53AM +0530, Sughosh Ganu wrote:
> > Changes since v1:
> > A new patch has been added to reflect the library class added for
> > changing the MMU attributes in StandaloneMM image, based on review
> > comments from Ard Biesheuvel.
> >
> >
> > These patches needs to be applied on top of the following patch series
> > - "ArmPkg related changes for StandaloneMM package".
> >
> >
> > Sughosh Ganu (2):
> > StandaloneMM: Include the newly added library class for MMU functions
> > StandaloneMM: Update permissions for Standalone MM drivers memory area
> >
> > .../StandaloneMmCoreEntryPoint.inf | 2 +-
> > .../StandaloneMmPeCoffExtraActionLib.inf | 18 +-
> > .../StandaloneMmPeCoffExtraActionLib.c | 222 +++++++++++++++++++++
> > 3 files changed, 234 insertions(+), 8 deletions(-)
> > copy ArmPkg/Library/RvdPeCoffExtraActionLib/RvdPeCoffExtraActionLib.inf => StandaloneMmPkg/Library/StandaloneMmPeCoffExtraActionLib/StandaloneMmPeCoffExtraActionLib.inf (72%)
> > create mode 100644 StandaloneMmPkg/Library/StandaloneMmPeCoffExtraActionLib/StandaloneMmPeCoffExtraActionLib.c
> >
> > --
> > 2.7.4
> >
--
-sughosh
next prev parent reply other threads:[~2018-12-01 4:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 6:22 [PATCH v2 0/2] StandaloneMM: Update permissions for Standalone MM drivers memory area Sughosh Ganu
2018-11-27 6:22 ` [PATCH v2 1/2] StandaloneMM: Include the newly added library class for MMU functions Sughosh Ganu
2018-11-27 6:22 ` [PATCH v2 2/2] StandaloneMM: Update permissions for Standalone MM drivers memory area Sughosh Ganu
2018-11-30 23:38 ` [PATCH v2 0/2] " Achin Gupta
2018-12-01 4:26 ` Sughosh Ganu [this message]
2018-12-01 18:45 ` Achin Gupta
2018-12-03 6:23 ` Sughosh Ganu
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=20181201042652.GA29905@arm.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