From: Mark Rutland <mark.rutland@arm.com>
To: Ard Biesheuvel <ardb@google.com>
Cc: linux-arm-kernel@lists.infradead.org,
Ard Biesheuvel <ardb@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v2 0/3] arm64 kpti fixes
Date: Mon, 27 Nov 2023 12:47:22 +0000 [thread overview]
Message-ID: <ZWSP2q6fTpBQ-ew9@FVFF77S0Q05N> (raw)
In-Reply-To: <20231127120049.2258650-5-ardb@google.com>
On Mon, Nov 27, 2023 at 01:00:50PM +0100, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> A couple of fixes and tweaks for KPTI - the first patch is a true
> regression in v6.7, the others are minor tweaks.
>
> v2:
> - add two more tweaks
> - use correct method to test system cap before alternatives have been
> applied
> - move check into kpti_install_ng_mappings()
>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Mark Rutland <mark.rutland@arm.com>
Thanks for this! For the series:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Mark.
>
> Ard Biesheuvel (3):
> arm64: Avoid enabling KPTI unnecessarily
> arm64: mm: Only map KPTI trampoline if it is going to be used
> arm64: Kconfig: drop KAISER reference from KPTI option description
>
> arch/arm64/Kconfig | 2 +-
> arch/arm64/kernel/cpufeature.c | 4 ++++
> arch/arm64/mm/mmu.c | 3 +++
> 3 files changed, 8 insertions(+), 1 deletion(-)
>
> --
> 2.43.0.rc1.413.gea7ed67945-goog
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-27 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 12:00 [PATCH v2 0/3] arm64 kpti fixes Ard Biesheuvel
2023-11-27 12:00 ` [PATCH v2 1/3] arm64: Avoid enabling KPTI unnecessarily Ard Biesheuvel
2023-11-27 15:48 ` Will Deacon
2023-11-27 15:52 ` Ard Biesheuvel
2023-11-27 16:31 ` Will Deacon
2023-11-27 16:39 ` Ard Biesheuvel
2023-11-27 16:41 ` Will Deacon
2023-11-27 17:49 ` Mark Rutland
2023-11-28 11:03 ` Will Deacon
2023-11-28 14:13 ` Mark Rutland
2023-12-11 11:39 ` Will Deacon
2023-12-12 17:16 ` Mark Rutland
2023-11-28 11:06 ` Will Deacon
2023-11-27 12:00 ` [PATCH v2 2/3] arm64: mm: Only map KPTI trampoline if it is going to be used Ard Biesheuvel
2023-11-27 12:00 ` [PATCH v2 3/3] arm64: Kconfig: drop KAISER reference from KPTI option description Ard Biesheuvel
2023-11-27 12:47 ` Mark Rutland [this message]
2023-11-30 19:14 ` (subset) [PATCH v2 0/3] arm64 kpti fixes Catalin Marinas
2023-12-11 20:27 ` 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=ZWSP2q6fTpBQ-ew9@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=ardb@google.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--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