linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@kernel.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Hector Martin <marcan@marcan.st>,
	 Mark Rutland <mark.rutland@arm.com>,
	Will Deacon <will@kernel.org>,
	 Catalin Marinas <catalin.marinas@arm.com>,
	Android Kernel Team <kernel-team@android.com>
Subject: Re: [PATCH v3 3/3] arm64: Get rid of CONFIG_ARM64_VHE
Date: Thu, 8 Apr 2021 23:47:38 +0200	[thread overview]
Message-ID: <CAK8P3a2+=LjnLtgvGx3s9i3X_9ypHZ6pEfObcjBtV2sVRrTmzw@mail.gmail.com> (raw)
In-Reply-To: <20210408131010.1109027-4-maz@kernel.org>

On Thu, Apr 8, 2021 at 3:10 PM Marc Zyngier <maz@kernel.org> wrote:
>
> CONFIG_ARM64_VHE was introduced with ARMv8.1 (some 7 years ago),
> and has been enabled by default for almost all that time.
>
> Given that newer systems that are VHE capable are finally becoming
> available, and that some systems are even incapable of not running VHE,
> drop the configuration altogether.
>
> Anyone willing to stick to non-VHE on VHE hardware for obscure
> reasons should use the 'kvm-arm.mode=nvhe' command-line option.

Have you considered adding options to do the reverse logic for this
and other features, such as making support for the old non-VHE
optional at compile time?

I understand that so far the rule is (almost) always that an arm64 kernel
should run on any Armv8.0-A or higher system regardless of configuration,
but the now announced Armv9.0-A definition might be the chance to
introduce the concept of a minimum level the way we do on other
architectures (e.g. armv6/v6k/v7 or k8/pentium4/core2/atom/generic).

The way I can see this working would be to have a single user-visible
option that controls whether the kernel supports only Armv9.0-A/Armv8.5-A
and assumes all mandatory features of that are present, or it remains
as before and supports all implementations back to the first v8.

This would help eliminate the runtime detection for not just VHE but
also LSE, LPA, PAN, etc. Not sure how significant the cost of any of
those are in terms of runtime performance and/or code size, but it
would feel nice to be able to build a kernel that can actually rely
on sane hardware features even if it will take a few more years before
that hardware becomes common enough to actually get some distros
ship a kernel that requires v8.5/v9.0.

        Arnd

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

  parent reply	other threads:[~2021-04-08 21:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 13:10 [PATCH v3 0/3] arm64: Dealing with VHE-only CPUs Marc Zyngier
2021-04-08 13:10 ` [PATCH v3 1/3] arm64: cpufeature: Allow early filtering of feature override Marc Zyngier
2021-04-08 13:10 ` [PATCH v3 2/3] arm64: Cope with CPUs stuck in VHE mode Marc Zyngier
2021-04-08 13:10 ` [PATCH v3 3/3] arm64: Get rid of CONFIG_ARM64_VHE Marc Zyngier
2021-04-08 16:59   ` Will Deacon
2021-04-08 17:24     ` Marc Zyngier
2021-04-08 21:47   ` Arnd Bergmann [this message]
2021-04-09  8:28     ` Marc Zyngier
2021-04-08 18:00 ` [PATCH v3 0/3] arm64: Dealing with VHE-only CPUs Catalin Marinas
2021-04-08 18:08   ` Marc Zyngier

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='CAK8P3a2+=LjnLtgvGx3s9i3X_9ypHZ6pEfObcjBtV2sVRrTmzw@mail.gmail.com' \
    --to=arnd@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kernel-team@android.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marcan@marcan.st \
    --cc=mark.rutland@arm.com \
    --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;
as well as URLs for NNTP newsgroup(s).