public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Ard Biesheuvel <ardb@google.com>,
	linux-arm-kernel@lists.infradead.org,
	Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>
Subject: Re: [PATCH v2 1/3] arm64: Avoid enabling KPTI unnecessarily
Date: Tue, 12 Dec 2023 17:16:12 +0000	[thread overview]
Message-ID: <ZXiVXLTYbAgfZcte@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <20231211113939.GA24899@willie-the-truck>

On Mon, Dec 11, 2023 at 11:39:39AM +0000, Will Deacon wrote:
> On Tue, Nov 28, 2023 at 02:13:16PM +0000, Mark Rutland wrote:
> > On Tue, Nov 28, 2023 at 11:03:40AM +0000, Will Deacon wrote:
> > > On Mon, Nov 27, 2023 at 05:49:21PM +0000, Mark Rutland wrote:
> > > > If you want these cases moves back to alternatives-based feature check helpers,
> > > > I can go do that.
> > > 
> > > I was thinking of something like the diff below to start with.
> > 
> > Sure; as-is that breaks the hyp offset patching, and we'll need ensure we still
> > call hyp_mode_check() before apply_alternatives_all(). In hyp_mode_check() we
> > call kvm_compute_layout(), which generates the 'va_mask', 'tag_val', and
> > 'tag_lsb' values which are used by the kvm_update_va_mask() patching callback
> > (for kern_hyp_va() and __kern_hyp_va()).
> > 
> > I think that can be moved before enable_cpu_capabilities() ratehr than needing
> > to be between enable_cpu_capabilities() and apply_alternatives_all(), but I'll
> > need to go digging to make certain.
> > 
> > Do you want this as a cleanup for v6.7-rc*, or as something to queue for
> > v6.8-rc1?
> 
> Sorry, I keep forgetting to reply to this after we spoke in-person. If
> you're able to spin something in the next day or so, I can pick it up for
> the next merge window. In the meantime, I'll grab Ard's changes so this can
> go on top.

I've sent that to:

  https://lore.kernel.org/linux-arm-kernel/20231212170910.3745497-1-mark.rutland@arm.com/

... based on the arm64 for-next/fixes branch.

Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2023-12-12 17:16 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 [this message]
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 ` [PATCH v2 0/3] arm64 kpti fixes Mark Rutland
2023-11-30 19:14 ` (subset) " 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=ZXiVXLTYbAgfZcte@FVFF77S0Q05N.cambridge.arm.com \
    --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