From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: Alexandru Elisei <alexandru.elisei@arm.com>,
Christoffer Dall <christoffer.dall@arm.com>,
Quentin Perret <qperret@google.com>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kernel-team@android.com, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] KVM/arm64 fixes for 5.18, take #2
Date: Fri, 29 Apr 2022 17:39:20 +0200 [thread overview]
Message-ID: <e0967ca4-b574-2be4-55de-3dce212fea21@redhat.com> (raw)
In-Reply-To: <20220429153615.710743-1-maz@kernel.org>
On 4/29/22 17:36, Marc Zyngier wrote:
> Paolo,
>
> Here's a trio of fixes for 5.18. Nothing terribly interesting, but
> nonetheless important fixes (two of the bugs are related to AArch32).
Cool, will pull soon. Please take a quick look at the flags->data ABI
fix, it's one patch on top of 5.18 as you requested and if I hear
nothing I'll send it ~Sunday morning to Linus.
Thanks,
Paolo
> Please pull,
>
> M.
>
> The following changes since commit 21db83846683d3987666505a3ec38f367708199a:
>
> selftests: KVM: Free the GIC FD when cleaning up in arch_timer (2022-04-07 08:46:13 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.18-2
>
> for you to fetch changes up to 85ea6b1ec915c9dd90caf3674b203999d8c7e062:
>
> KVM: arm64: Inject exception on out-of-IPA-range translation fault (2022-04-27 23:02:23 +0100)
>
> ----------------------------------------------------------------
> KVM/arm64 fixes for 5.18, take #2
>
> - Take care of faults occuring between the PARange and
> IPA range by injecting an exception
>
> - Fix S2 faults taken from a host EL0 in protected mode
>
> - Work around Oops caused by a PMU access from a 32bit
> guest when PMU has been created. This is a temporary
> bodge until we fix it for good.
>
> ----------------------------------------------------------------
> Alexandru Elisei (1):
> KVM/arm64: Don't emulate a PMU for 32-bit guests if feature not set
>
> Marc Zyngier (1):
> KVM: arm64: Inject exception on out-of-IPA-range translation fault
>
> Will Deacon (1):
> KVM: arm64: Handle host stage-2 faults from 32-bit EL0
>
> arch/arm64/include/asm/kvm_emulate.h | 1 +
> arch/arm64/kvm/hyp/nvhe/host.S | 18 +++++++++---------
> arch/arm64/kvm/inject_fault.c | 28 ++++++++++++++++++++++++++++
> arch/arm64/kvm/mmu.c | 19 +++++++++++++++++++
> arch/arm64/kvm/pmu-emul.c | 23 ++++++++++++++++++++++-
> 5 files changed, 79 insertions(+), 10 deletions(-)
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-04-29 15:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 15:36 [GIT PULL] KVM/arm64 fixes for 5.18, take #2 Marc Zyngier
2022-04-29 15:39 ` Paolo Bonzini [this message]
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=e0967ca4-b574-2be4-55de-3dce212fea21@redhat.com \
--to=pbonzini@redhat.com \
--cc=alexandru.elisei@arm.com \
--cc=christoffer.dall@arm.com \
--cc=james.morse@arm.com \
--cc=kernel-team@android.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=qperret@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/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