From: Marc Zyngier <maz@kernel.org>
To: linux-arm-kernel@lists.infradead.org,
<kvmarm@lists.cs.columbia.edu>, <kvmarm@lists.linux.dev>,
kvm@vger.kernel.org
Cc: D Scott Phillips <scott@os.amperecomputing.com>,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
James Morse <james.morse@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 and optimisations
Date: Thu, 12 Jan 2023 12:38:26 +0000 [thread overview]
Message-ID: <20230112123829.458912-1-maz@kernel.org> (raw)
Having been busy on the NV front the past few weeks, I collected a
small set of fixes/improvements that make sense even outside of NV.
The first one is an interesting fix (actually a regression introduced
by the initial set of NV-related patches) reported by Scott and
Ganapatrao, where we fail to recognise that a timer that has fired
doesn't need to fire again. And again.
The second patch is a definite performance improvement on nVHE systems
when accessing the emulated physical timer. It also makes NV bearable
in some conditions (with FEAT_ECV, for example).
The last patch is more of a sanity check. There is no reason to BUG()
if we can avoid it at all and kill the guest instead!
These patches are 6.3 candidates, although the first one could be a
6.2 fix.
M.
Marc Zyngier (3):
KVM: arm64: Don't arm a hrtimer for an already pending timer
KVM: arm64: Reduce overhead of trapped timer sysreg accesses
KVM: arm64: timers: Don't BUG() on unhandled timer trap
arch/arm64/kvm/arch_timer.c | 77 +++++++++++++++++++++++--------------
arch/arm64/kvm/sys_regs.c | 4 +-
2 files changed, 52 insertions(+), 29 deletions(-)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-01-12 12:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 12:38 Marc Zyngier [this message]
2023-01-12 12:38 ` [PATCH 1/3] KVM: arm64: Don't arm a hrtimer for an already pending timer Marc Zyngier
2023-01-12 12:38 ` [PATCH 2/3] KVM: arm64: Reduce overhead of trapped timer sysreg accesses Marc Zyngier
2023-01-12 12:38 ` [PATCH 3/3] KVM: arm64: timers: Don't BUG() on unhandled timer trap Marc Zyngier
2023-01-30 18:30 ` [PATCH 0/3] KVM: arm64: timer fixes and optimisations 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=20230112123829.458912-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=gankulkarni@os.amperecomputing.com \
--cc=james.morse@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oliver.upton@linux.dev \
--cc=scott@os.amperecomputing.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;
as well as URLs for NNTP newsgroup(s).