[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YAwvi9zEXZxbo9iK@Catalins-MacBook-Air.local>
Date: Sat, 23 Jan 2021 14:15:39 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: Marc Zyngier <maz@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
linux-kernel@...r.kernel.org, Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
David Brazdil <dbrazdil@...gle.com>,
Alexandru Elisei <alexandru.elisei@....com>,
Ard Biesheuvel <ardb@...nel.org>,
Jing Zhang <jingzhangos@...gle.com>,
Ajay Patil <pajay@....qualcomm.com>,
Prasad Sodagudi <psodagud@...eaurora.org>,
Srinivas Ramana <sramana@...eaurora.org>,
James Morse <james.morse@....com>,
Julien Thierry <julien.thierry.kdev@...il.com>,
Suzuki K Poulose <suzuki.poulose@....com>,
kernel-team@...roid.com
Subject: Re: [PATCH v4 16/21] arm64: Make kvm-arm.mode={nvhe,protected} an
alias of id_aa64mmfr1.vh=0
On Mon, Jan 18, 2021 at 09:45:28AM +0000, Marc Zyngier wrote:
> Admitedly, passing id_aa64mmfr1.vh=0 on the command-line isn't
> that easy to understand, and it is likely that users would much
> prefer write "kvm-arm.mode=nvhe", or "...=protected".
>
> So here you go. This has the added advantage that we can now
> always honor the "kvm-arm.mode=protected" option, even when
> booting on a VHE system.
>
> Signed-off-by: Marc Zyngier <maz@...nel.org>
Acked-by: Catalin Marinas <catalin.marinas@....com>
Powered by blists - more mailing lists