From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Anshuman Khandual <anshuman.khandual@arm.com>,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
James Morse <james.morse@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Oliver Upton <oliver.upton@linux.dev>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 6.6, take #2
Date: Fri, 13 Oct 2023 22:30:53 +0100 [thread overview]
Message-ID: <20231013213053.3947696-1-maz@kernel.org> (raw)
Paolo,
Here's a set of additional fixes for 6.6. The most important part is
the fix for a breakage of the Permission Indirection feature, which is
a regression. The other (less important) part is a fix for the physical
timer offset.
Please pull,
M.
The following changes since commit 373beef00f7d781a000b12c31fb17a5a9c25969c:
KVM: arm64: nvhe: Ignore SVE hint in SMCCC function ID (2023-09-12 13:07:37 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-6.6-2
for you to fetch changes up to 9404673293b065cbb16b8915530147cac7e80b4d:
KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2 (2023-10-12 16:55:21 +0100)
----------------------------------------------------------------
KVM/arm64 fixes for 6.6, take #2
- Fix the handling of the phycal timer offset when FEAT_ECV
and CNTPOFF_EL2 are implemented.
- Restore the functionnality of Permission Indirection that
was broken by the Fine Grained Trapping rework
- Cleanup some PMU event sharing code
----------------------------------------------------------------
Anshuman Khandual (1):
KVM: arm64: pmu: Drop redundant check for non-NULL kvm_pmu_events
Joey Gouly (2):
KVM: arm64: Add nPIR{E0}_EL1 to HFG traps
KVM: arm64: POR{E0}_EL1 do not need trap handlers
Marc Zyngier (1):
KVM: arm64: timers: Correctly handle TGE flip with CNTPOFF_EL2
arch/arm64/include/asm/kvm_arm.h | 4 ++--
arch/arm64/kvm/arch_timer.c | 13 +++---------
arch/arm64/kvm/emulate-nested.c | 2 ++
arch/arm64/kvm/hyp/vhe/switch.c | 44 ++++++++++++++++++++++++++++++++++++++++
arch/arm64/kvm/pmu.c | 4 ++--
arch/arm64/kvm/sys_regs.c | 4 ++--
include/kvm/arm_arch_timer.h | 7 +++++++
7 files changed, 62 insertions(+), 16 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-10-13 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 21:30 Marc Zyngier [this message]
2023-10-15 12:23 ` [GIT PULL] KVM/arm64 fixes for 6.6, take #2 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=20231013213053.3947696-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=james.morse@arm.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--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;
as well as URLs for NNTP newsgroup(s).