From: Vabhav Sharma <vabhav.sharma@nxp.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: SError Exception and HCR_EL2 Usage
Date: Mon, 9 Oct 2017 17:33:05 +0000 [thread overview]
Message-ID: <DB4PR04MB299F2A707A0990558BC87D0F3740@DB4PR04MB299.eurprd04.prod.outlook.com> (raw)
Dear Experts,
I am facing SError exception during UEFI bring-up.
At boot , secure f/w starts in EL3 and loads UEFI image to DDR. After this secure f/w passes control to UEFI in EL2.
I debugged and manifest the problem by adding below lines in UEFI PrePi entry point(ModuleEntryPoint.S)
ASM_FUNC(_ModuleEntryPoint)
+msr daifclr,#4
+isb
+mrs x0, hcr_el2
+ldr x1, =0x08000000
+orr x0, x0, x1
+msr hcr_el2, x0
+isb
Once exception occurs than ELR_EL2 point to 'isb' instruction and ESR_EL2 is SError Exception syndrome.
Could you please suggest if this is UEFI problem or Secure f/w issue?
Additionally, TGE bit is set in hcr_el2 three times during PrePei phase(ArmPlatformPkg/PrePi/AArch64/ArchPrePi.c),DxeMain(),ArmCpuDxe.
Please explain the purpose of setting it or require to be fixed?
Regards,
Vabhav
next reply other threads:[~2017-10-09 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 17:33 Vabhav Sharma [this message]
2017-10-09 19:15 ` SError Exception and HCR_EL2 Usage Ard Biesheuvel
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=DB4PR04MB299F2A707A0990558BC87D0F3740@DB4PR04MB299.eurprd04.prod.outlook.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