From: Paolo Bonzini <pbonzini@redhat.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kvm@vger.kernel.org, kernel-team@android.com,
Steven Price <steven.price@arm.com>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [GIT PULL] KVM/arm64 fixes for 5.8, take #2
Date: Wed, 1 Jul 2020 16:24:39 +0200 [thread overview]
Message-ID: <733910d5-b4db-3df5-9589-80e0367311fd@redhat.com> (raw)
In-Reply-To: <20200629162519.825200-1-maz@kernel.org>
On 29/06/20 18:25, Marc Zyngier wrote:
> Hi Paolo,
>
> Here's another pull request for a handful of KVM/arm64 fixes. Nothing
> absolutely critical (see the tag for the gory details), but I'd rather
> get these merged as soon as possible.
>
> Please pull,
>
> M.
>
> The following changes since commit b3a9e3b9622ae10064826dccb4f7a52bd88c7407:
>
> Linux 5.8-rc1 (2020-06-14 12:45:04 -0700)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git kvmarm-fixes-5.8-2
>
> for you to fetch changes up to a3f574cd65487cd993f79ab235d70229d9302c1e:
>
> KVM: arm64: vgic-v4: Plug race between non-residency and v4.1 doorbell (2020-06-23 11:24:39 +0100)
>
> ----------------------------------------------------------------
> KVM/arm fixes for 5.8, take #2
>
> - Make sure a vcpu becoming non-resident doesn't race against the doorbell delivery
> - Only advertise pvtime if accounting is enabled
> - Return the correct error code if reset fails with SVE
> - Make sure that pseudo-NMI functions are annotated as __always_inline
>
> ----------------------------------------------------------------
> Alexandru Elisei (1):
> KVM: arm64: Annotate hyp NMI-related functions as __always_inline
>
> Andrew Jones (1):
> KVM: arm64: pvtime: Ensure task delay accounting is enabled
>
> Marc Zyngier (1):
> KVM: arm64: vgic-v4: Plug race between non-residency and v4.1 doorbell
>
> Steven Price (1):
> KVM: arm64: Fix kvm_reset_vcpu() return code being incorrect with SVE
>
> arch/arm64/include/asm/arch_gicv3.h | 2 +-
> arch/arm64/include/asm/cpufeature.h | 2 +-
> arch/arm64/kvm/pvtime.c | 15 ++++++++++++---
> arch/arm64/kvm/reset.c | 10 +++++++---
> arch/arm64/kvm/vgic/vgic-v4.c | 8 ++++++++
> drivers/irqchip/irq-gic-v3-its.c | 8 ++++++++
> 6 files changed, 37 insertions(+), 8 deletions(-)
>
Pulled, thanks.
Paolo
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
prev parent reply other threads:[~2020-07-01 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 16:25 [GIT PULL] KVM/arm64 fixes for 5.8, take #2 Marc Zyngier
2020-06-29 16:25 ` [PATCH 1/4] KVM: arm64: Annotate hyp NMI-related functions as __always_inline Marc Zyngier
2020-06-29 16:25 ` [PATCH 2/4] KVM: arm64: Fix kvm_reset_vcpu() return code being incorrect with SVE Marc Zyngier
2020-06-29 16:25 ` [PATCH 3/4] KVM: arm64: pvtime: Ensure task delay accounting is enabled Marc Zyngier
2020-06-29 16:25 ` [PATCH 4/4] KVM: arm64: vgic-v4: Plug race between non-residency and v4.1 doorbell Marc Zyngier
2020-07-01 14:24 ` 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=733910d5-b4db-3df5-9589-80e0367311fd@redhat.com \
--to=pbonzini@redhat.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=steven.price@arm.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).