From: Anshuman Khandual <anshuman.khandual@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] docs: arm64: Document MDCR_EL3 boot requirements
Date: Wed, 11 Dec 2024 12:24:23 +0530 [thread overview]
Message-ID: <20241211065425.1106683-1-anshuman.khandual@arm.com> (raw)
This series adds missing MDCR_EL3 boot requirements for debug and pmu
registers that are currently being accessed in the kernel. Please refer
the following link for some earlier discussions on this.
https://lore.kernel.org/all/ZxfOeqyb3RvsdYbU@J2N7QTR9R3/
This series applies on v6.13-rc1
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Anshuman Khandual (2):
docs: arm64: Document EL3 requirements for cpu debug architecture
docs: arm64: Document EL3 requirements for FEAT_PMUv3
Documentation/arch/arm64/booting.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
--
2.30.2
next reply other threads:[~2024-12-11 6:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 6:54 Anshuman Khandual [this message]
2024-12-11 6:54 ` [PATCH 1/2] docs: arm64: Document EL3 requirements for cpu debug architecture Anshuman Khandual
2024-12-11 6:54 ` [PATCH 2/2] docs: arm64: Document EL3 requirements for FEAT_PMUv3 Anshuman Khandual
2024-12-18 7:49 ` [PATCH 0/2] docs: arm64: Document MDCR_EL3 boot requirements Anshuman Khandual
2024-12-19 19:47 ` Will Deacon
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=20241211065425.1106683-1-anshuman.khandual@arm.com \
--to=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will@kernel.org \
/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
all inboxes | Powered by JetHome®