From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
Mark Brown <broonie@kernel.org>, Oliver Upton <oupton@kernel.org>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] KVM/arm64 fix for 6.18, take #3
Date: Fri, 14 Nov 2025 11:34:15 +0000 [thread overview]
Message-ID: <20251114113415.3217950-1-maz@kernel.org> (raw)
Paolo,
I'm back with my weekly routine of collecting patches, plugging
another couple of regressions (the FGT one is particularly annoying).
I hope this is the last one for this cycle, but my gut feeling is that
we're not quite finished with it yet...
Please pull,
M.
The following changes since commit 4af235bf645516481a82227d82d1352b9788903a:
MAINTAINERS: Switch myself to using kernel.org address (2025-11-08 11:21:20 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.18-3
for you to fetch changes up to 85592114ffda568b507bc2b04f5e9afbe7c13b62:
KVM: arm64: VHE: Compute fgt traps before activating them (2025-11-12 10:52:58 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 6.18, take #3
- Only adjust the ID registers when no irqchip has been created once
per VM run, instead of doing it once per vcpu, as this otherwise
triggers a pretty bad conbsistency check failure in the sysreg code.
- Make sure the per-vcpu Fine Grain Traps are computed before we load
the system registers on the HW, as we otherwise start running without
anything set until the first preemption of the vcpu.
----------------------------------------------------------------
Alexandru Elisei (1):
KVM: arm64: VHE: Compute fgt traps before activating them
Marc Zyngier (1):
KVM: arm64: Finalize ID registers only once per VM
arch/arm64/kvm/arm.c | 2 +-
arch/arm64/kvm/sys_regs.c | 6 +++++-
2 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2025-11-14 11:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 11:34 Marc Zyngier [this message]
2025-11-18 16:38 ` [GIT PULL] KVM/arm64 fix for 6.18, take #3 Paolo Bonzini
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=20251114113415.3217950-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=alexandru.elisei@arm.com \
--cc=broonie@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--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