All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Subject: [bootwrapper PATCH 0/2] aarch64: Prepare EL3 for MDSELR_EL1
Date: Thu,  4 Apr 2024 13:07:24 +0530	[thread overview]
Message-ID: <20240404073726.947215-1-anshuman.khandual@arm.com> (raw)

MDSELR_EL1 register will be used to configure breakpoint and watchpoint
register banks when FEAT_Debugv8p9 is enabled. This series prepares EL3
for MDSELR_EL1 access traps into EL3, and into EL2 via new Fine Grained
Traps Enable 2 (FEAT_FGT2) registers.

Anshuman Khandual (2):
  aarch64: Disable trapping into EL3 while accessing MDSELR_EL1
  aarch64: Disable trapping into EL3 while accessing FEAT_FGT2 registers

 arch/aarch64/include/asm/cpu.h | 3 +++
 arch/aarch64/init.c            | 6 ++++++
 2 files changed, 9 insertions(+)

-- 
2.25.1


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

             reply	other threads:[~2024-04-04  7:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04  7:37 Anshuman Khandual [this message]
2024-04-04  7:37 ` [bootwrapper PATCH 1/2] aarch64: Disable trapping into EL3 while accessing MDSELR_EL1 Anshuman Khandual
2024-04-18 10:27   ` Mark Rutland
2024-04-19  2:21     ` Anshuman Khandual
2024-04-04  7:37 ` [bootwrapper PATCH 2/2] aarch64: Disable trapping into EL3 while accessing FEAT_FGT2 registers Anshuman Khandual
2024-04-18 10:40   ` Mark Rutland
2024-04-19  3:04     ` Anshuman Khandual
2024-04-17  3:25 ` [bootwrapper PATCH 0/2] aarch64: Prepare EL3 for MDSELR_EL1 Anshuman Khandual
2024-04-18 10:43   ` 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=20240404073726.947215-1-anshuman.khandual@arm.com \
    --to=anshuman.khandual@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.