From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: Kill ESR_LNX_EXEC
Date: Tue, 31 May 2016 12:33:00 +0100 [thread overview]
Message-ID: <1464694383-31700-1-git-send-email-mark.rutland@arm.com> (raw)
Currently we (ab)use a reserved bit in ESR_ELx for our own purposes as
ESR_LNX_EXEC, which isn't ideal, especially as we're inconsistent with our
mnemonic usage. This series removes ESR_LNX_EXEC entirely, avoiding (ab)use of
reserved ESR_ELx bits, and makes things a little more consistent.
I've extracted this from my entry-deasm branch [1], and rebased to v4.7-rc1.
I've split the KVM changes as the KVM code is undergoing rapid change these
days, and it should be possible to take those as a subsequent cleanup rather
than forcing a painful merging process.
Thanks,
Mark.
[1] https://git.kernel.org/cgit/linux/kernel/git/mark/linux.git/log/?h=arm64/entry-deasm
Mark Rutland (3):
arm64: add macro to extract ESR_ELx.EC
arm64/kvm: use ESR_ELx_EC to extract EC
arm64: kill ESR_LNX_EXEC
arch/arm64/include/asm/esr.h | 1 +
arch/arm64/include/asm/kvm_emulate.h | 2 +-
arch/arm64/kernel/entry.S | 2 +-
arch/arm64/kernel/traps.c | 2 +-
arch/arm64/kvm/handle_exit.c | 4 ++--
arch/arm64/kvm/hyp/switch.c | 2 +-
arch/arm64/mm/fault.c | 15 +++++++++------
7 files changed, 16 insertions(+), 12 deletions(-)
--
1.9.1
next reply other threads:[~2016-05-31 11:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 11:33 Mark Rutland [this message]
2016-05-31 11:33 ` [PATCH 1/3] arm64: add macro to extract ESR_ELx.EC Mark Rutland
2016-05-31 11:33 ` [PATCH 2/3] arm64/kvm: use ESR_ELx_EC to extract EC Mark Rutland
2016-05-31 14:35 ` Christoffer Dall
2016-05-31 11:33 ` [PATCH 3/3] arm64: kill ESR_LNX_EXEC Mark Rutland
2016-05-31 16:53 ` [PATCH 0/3] arm64: Kill ESR_LNX_EXEC Catalin Marinas
2016-06-02 18:21 ` Will Deacon
2016-06-06 10:59 ` Mark Rutland
2016-06-21 16:09 ` Catalin Marinas
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=1464694383-31700-1-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).