From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: nv: Unfudge ID_AA64PFR0_EL1 masking
Date: Sat, 22 Jun 2024 09:35:02 +0100 [thread overview]
Message-ID: <86zfrdide1.wl-maz@kernel.org> (raw)
In-Reply-To: <20240621224044.2465901-1-oliver.upton@linux.dev>
On Fri, 21 Jun 2024 23:40:44 +0100,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> Marc reports that L1 VMs aren't booting with the NV series applied to
> today's kvmarm/next. After bisecting the issue, it appears that
> 44241f34fac9 ("KVM: arm64: nv: Use accessors for modifying ID
> registers") is to blame.
>
> Poking around at the issue a bit further, it'd appear that the value for
> ID_AA64PFR0_EL1 is complete garbage, as 'val' still contains the value
> we set ID_AA64ISAR1_EL1 to.
>
> Fix the read-modify-write pattern to actually use ID_AA64PFR0_EL1 as the
> starting point. Excuse me as I return to my shame cube.
>
> Reported-by: Marc Zyngier <maz@kernel.org>
> Fixes: 44241f34fac9 ("KVM: arm64: nv: Use accessors for modifying ID registers")
> Signed-off-by: Oliver Upton <oliver.upton@linux.dev>
Confirmed, we're back in business.
Acked-by: Marc Zyngier <maz@kernel.org>
Tested-by: Marc Zyngier <maz@kernel.org>
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-06-22 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 22:40 [PATCH] KVM: arm64: nv: Unfudge ID_AA64PFR0_EL1 masking Oliver Upton
2024-06-22 8:35 ` Marc Zyngier [this message]
2024-06-22 18:11 ` Oliver Upton
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=86zfrdide1.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.