From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] arm64: Kill ESR_LNX_EXEC
Date: Tue, 21 Jun 2016 17:09:09 +0100 [thread overview]
Message-ID: <20160621160908.GF14542@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1464694383-31700-1-git-send-email-mark.rutland@arm.com>
On Tue, May 31, 2016 at 12:33:00PM +0100, Mark Rutland wrote:
> 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
I queued these 3 patches for 4.8. Thanks.
--
Catalin
prev parent reply other threads:[~2016-06-21 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 11:33 [PATCH 0/3] arm64: Kill ESR_LNX_EXEC Mark Rutland
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 [this message]
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=20160621160908.GF14542@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@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).