public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexandru Elisei <alexandru.elisei@arm.com>
To: Suzuki K Poulose <suzuki.poulose@arm.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-arm-kernel@lists.infradead.org
Cc: mark.rutland@arm.com, Andre.Przywara@arm.com, james.morse@arm.com
Subject: Re: [boot-wrapper] [PATCH] aarch64: Enable TRBE for the non-secure world
Date: Fri, 12 Feb 2021 17:28:58 +0000	[thread overview]
Message-ID: <353f247b-4fa9-298d-c8cf-b43aa4b0a860@arm.com> (raw)
In-Reply-To: <81d47675-c628-1bb9-d410-46579f4b5175@arm.com>

Hi,

On 2/12/21 3:44 PM, Suzuki K Poulose wrote:
> On 2/12/21 2:31 PM, Alexandru Elisei wrote:
>> Hello Anshuman,
>>
>> On 2/11/21 11:26 AM, Anshuman Khandual wrote:
>>> MDCR_EL3.NSTB resets to an UNKNOWN value. Configure it to allow the trace
>>> buffer to use non-secure memory and to permit direct register accesses from
>>> the non-secure world. Before that, just check AA64DFR0_EL1.TraceBuffer and
>>> make sure TRBE is implemented. We still continue to reset MDCR_EL3 register
>>> to zero with the exception of MDCR_EL3.NSPB and MDCR_EL3.NSTB.
>>>
>>> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
>>> ---
>>>   arch/aarch64/boot.S | 8 ++++++++
>>>   1 file changed, 8 insertions(+)
>>>
>>> diff --git a/arch/aarch64/boot.S b/arch/aarch64/boot.S
>>> index 37f4b98..e47cf59 100644
>>> --- a/arch/aarch64/boot.S
>>> +++ b/arch/aarch64/boot.S
>>> @@ -71,6 +71,14 @@ _start:
>>>       ldr    x1, =(0x3 << 12)
>>>       orr    x0, x0, x1
>>>   +1:    mrs    x1, id_aa64dfr0_el1
>>> +    ubfx    x1, x1, #44, #4
>>> +    cbz    x1, 1f
>>> +
>>> +    // Enable TRBE for the non-secure world.
>>> +    ldr    x1, =(0x3 << 24)
>>> +    orr    x0, x0, x1
>>> +
>>>   1:    msr    mdcr_el3, x0            // Disable traps to EL3
>>>         mrs    x0, id_aa64pfr0_el1
>>
>> That's strange, I'm looking at ARM DDI 0487G.a and bits [44:47] from
>> ID_AA64DFR0_EL1 are RES0 and there is no TraceBuffer field; bits [24:25] of
>> MDCR_EL3 are also RES0 and I searched the entire file for the NSTB field, could
>> not find it. Do I have an outdated version of the architecture?
>
> They are not in the Arm ARM. These are part of the Future Architecture
> technology changes, for which the register defintions are available here :
>
> https://developer.arm.com/documentation/ddi0601/2020-12/AArch64-Registers/

That worked, thanks!

Thanks,

Alex

>
> Cheers
> Suzuki
>
>>
>> Thanks,
>>
>> Alex
>>
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-02-12 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 11:26 [boot-wrapper] [PATCH] aarch64: Enable TRBE for the non-secure world Anshuman Khandual
2021-02-12 14:31 ` Alexandru Elisei
2021-02-12 15:44   ` Suzuki K Poulose
2021-02-12 17:28     ` Alexandru Elisei [this message]
2021-02-12 17:33 ` Alexandru Elisei
2021-02-25 18:33   ` Mark Rutland
2021-02-25 18:30 ` Mark Rutland

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=353f247b-4fa9-298d-c8cf-b43aa4b0a860@arm.com \
    --to=alexandru.elisei@arm.com \
    --cc=Andre.Przywara@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=suzuki.poulose@arm.com \
    /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