From: Oliver Upton <oliver.upton@linux.dev>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH] KVM: arm64: Rationalise KVM banner output
Date: Mon, 1 Apr 2024 01:47:27 -0700 [thread overview]
Message-ID: <171196113083.400673.3068319808641697222.b4-ty@linux.dev> (raw)
In-Reply-To: <20240321173706.3280796-1-maz@kernel.org>
On Thu, 21 Mar 2024 17:37:06 +0000, Marc Zyngier wrote:
> We are not very consistent when it comes to displaying which mode
> we're in (VHE, {n,h}VHE, protected or not). For example, booting
> in protected mode with hVHE results in:
>
> [ 0.969545] kvm [1]: Protected nVHE mode initialized successfully
>
> which is mildly amusing considering that the machine is VHE only.
>
> [...]
Applied to kvmarm/fixes, thanks!
[1/1] KVM: arm64: Rationalise KVM banner output
commit: d96c66ab9fb3ad8b243669cf6b41e68d0f7f9ecd
--
Best,
Oliver
prev parent reply other threads:[~2024-04-01 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 17:37 [PATCH] KVM: arm64: Rationalise KVM banner output Marc Zyngier
2024-04-01 8:47 ` Oliver Upton [this message]
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=171196113083.400673.3068319808641697222.b4-ty@linux.dev \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.com \
/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