From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Cc: Wei-Lin Chang <r09922117@csie.ntu.edu.tw>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>,
Dmytro Terletskyi <Dmytro_Terletskyi@epam.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: [PATCH 0/3] KVM/arm64: timer fixes for 6.14
Date: Tue, 28 Jan 2025 16:17:18 +0000 [thread overview]
Message-ID: <20250128161721.3279927-1-maz@kernel.org> (raw)
It's been recently pointed out that the NV timer code that is
(hopefully) on its way upstream is marginally sub-optimal (read:
terminally broken). This short series attempts to fix things:
- Correctly arm a background timer in all situations
- Avoid corrupting the EL2 state by shoving the EL1 state into it, and
simplify the handling of emulated timers
- Make the NV init of the timers less awkward and expensive
Thanks to Volodymyr Babchuk and Wei-Lin Chang for their help.
Patches on top of kvmarm-6.14, and merged back on top of my
kvm-arm64/nv-next branch.
Marc Zyngier (3):
KVM: arm64: timer: Always evaluate the need for a soft timer
KVM: arm64: timer: Correctly handle EL1 timer emulation when !FEAT_ECV
KVM: arm64: timer: Consolidate NV configuration of virtual timers
arch/arm64/kvm/arch_timer.c | 82 ++++++++++++++----------------------
arch/arm64/kvm/arm.c | 3 ++
include/kvm/arm_arch_timer.h | 1 +
3 files changed, 36 insertions(+), 50 deletions(-)
--
2.39.2
next reply other threads:[~2025-01-28 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 16:17 Marc Zyngier [this message]
2025-01-28 16:17 ` [PATCH 1/3] KVM: arm64: timer: Always evaluate the need for a soft timer Marc Zyngier
2025-02-04 14:08 ` Dmytro Terletskyi
2025-01-28 16:17 ` [PATCH 2/3] KVM: arm64: timer: Correctly handle EL1 timer emulation when !FEAT_ECV Marc Zyngier
2025-02-04 14:10 ` Dmytro Terletskyi
2025-01-28 16:17 ` [PATCH 3/3] KVM: arm64: timer: Consolidate NV configuration of virtual timers Marc Zyngier
2025-01-30 21:41 ` Oliver Upton
2025-01-31 8:46 ` Marc Zyngier
2025-02-04 14:15 ` Dmytro Terletskyi
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=20250128161721.3279927-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=Dmytro_Terletskyi@epam.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=r09922117@csie.ntu.edu.tw \
--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;
as well as URLs for NNTP newsgroup(s).