From: Oliver Upton <oliver.upton@linux.dev>
To: pbonzini@redhat.com
Cc: maz@kernel.org, reijiw@google.com, joey.gouly@arm.com,
james.morse@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, kvmarm@lists.linux.dev,
kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 6.3, part #1
Date: Sat, 11 Mar 2023 13:41:10 -0800 [thread overview]
Message-ID: <ZAz1duOOOTu+5LW5@thinky-boi> (raw)
Hi Paolo,
First shot at sending a pull request to you, please let me know if anything
is screwed up :)
A single, important fix for guest timers addressing a bug from the nested
virtualization prefix that went in 6.3.
Please pull,
--
Oliver
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.3-1
for you to fetch changes up to 47053904e18282af4525a02e3e0f519f014fc7f9:
KVM: arm64: timers: Convert per-vcpu virtual offset to a global value (2023-03-11 02:00:40 -0800)
----------------------------------------------------------------
KVM/arm64 fixes for 6.3, part #1
A single patch to address a rather annoying bug w.r.t. guest timer
offsetting. Effectively the synchronization of timer offsets between
vCPUs was broken, leading to inconsistent timer reads within the VM.
----------------------------------------------------------------
Marc Zyngier (1):
KVM: arm64: timers: Convert per-vcpu virtual offset to a global value
arch/arm64/include/asm/kvm_host.h | 3 +++
arch/arm64/kvm/arch_timer.c | 45 +++++++++------------------------------
arch/arm64/kvm/hypercalls.c | 2 +-
include/kvm/arm_arch_timer.h | 15 +++++++++++++
4 files changed, 29 insertions(+), 36 deletions(-)
next reply other threads:[~2023-03-11 21:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 21:41 Oliver Upton [this message]
2023-03-14 11:34 ` [GIT PULL] KVM/arm64 fixes for 6.3, part #1 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=ZAz1duOOOTu+5LW5@thinky-boi \
--to=oliver.upton@linux.dev \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.com \
--cc=reijiw@google.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