From: Mark Brown <broonie@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Mark Brown <broonie@kernel.org>
Subject: [PATCH v1 0/2] arm64/asm: Remove DAIF save/restore macros
Date: Wed, 23 Nov 2022 18:02:07 +0000 [thread overview]
Message-ID: <20221123180209.634650-1-broonie@kernel.org> (raw)
As part of an effort to improve the maintainability of the code for
manipulating DAIF let's reduce the number of places where it is
implemented by lifting the masking done during TTBR1 replacement for
KPTI up into C code and removing the assembler macros it was using.
Due to a textual collision with the removal of enable_da this is based
on for-next/trivial in the arm64 tree.
Mark Brown (2):
arm64/kpti: Move DAIF masking to C code
arm64/asm: Remove unused assembler DAIF save/restore macros
arch/arm64/include/asm/assembler.h | 9 ---------
arch/arm64/include/asm/mmu_context.h | 10 ++++++++++
arch/arm64/mm/proc.S | 4 ----
3 files changed, 10 insertions(+), 13 deletions(-)
base-commit: 32d495b0c3305546f4773b9aafcd4e90188ddb9e
--
2.30.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-11-23 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 18:02 Mark Brown [this message]
2022-11-23 18:02 ` [PATCH v1 1/2] arm64/kpti: Move DAIF masking to C code Mark Brown
2022-11-24 10:58 ` Mark Rutland
2022-11-23 18:02 ` [PATCH v1 2/2] arm64/asm: Remove unused assembler DAIF save/restore macros Mark Brown
2022-11-24 10:59 ` Mark Rutland
2022-11-25 13:24 ` [PATCH v1 0/2] arm64/asm: Remove " 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=20221123180209.634650-1-broonie@kernel.org \
--to=broonie@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 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.