From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: catalin.marinas@arm.com, will.deacon@arm.com
Cc: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: Clear OS Double Lock Register
Date: Mon, 8 Apr 2019 18:17:17 +0100 [thread overview]
Message-ID: <20190408171719.44711-1-jean-philippe.brucker@arm.com> (raw)
Some firmwares may boot Linux with the OS Double Lock Register set to 1,
even though it normally resets to 0. This happens for example on my
ThunderX2 machine when hotplugging a CPU or rebooting via kexec. As a
result the affected CPU cannot generate debug exceptions from HW
breakpoints or single-step. Sanitize the OSDLR value on CPU boot and
resume.
Jean-Philippe Brucker (2):
arm64: Clear OS Double Lock on CPU boot
arm64: Save and restore OSDLR_EL1
arch/arm64/kernel/debug-monitors.c | 1 +
arch/arm64/mm/proc.S | 34 ++++++++++++++++--------------
2 files changed, 19 insertions(+), 16 deletions(-)
--
2.21.0
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-04-08 17:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:17 Jean-Philippe Brucker [this message]
2019-04-08 17:17 ` [PATCH 1/2] arm64: Clear OSDLR_EL1 on CPU boot Jean-Philippe Brucker
2019-04-08 17:17 ` [PATCH 2/2] arm64: Save and restore OSDLR_EL1 Jean-Philippe Brucker
2019-04-09 10:37 ` Will Deacon
2019-04-09 11:29 ` Jean-Philippe Brucker
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=20190408171719.44711-1-jean-philippe.brucker@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will.deacon@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;
as well as URLs for NNTP newsgroup(s).