From: Paolo Bonzini <pbonzini@redhat.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [GIT PULL] KVM changes for Linux 5.8-rc5
Date: Mon, 6 Jul 2020 13:15:23 -0400 [thread overview]
Message-ID: <20200706171523.12441-1-pbonzini@redhat.com> (raw)
Linus,
The following changes since commit e4553b4976d1178c13da295cb5c7b21f55baf8f9:
KVM: VMX: Remove vcpu_vmx's defunct copy of host_pkru (2020-06-23 06:01:29 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch changes up to 8038a922cf9af5266eaff29ce996a0d1b788fc0d:
Merge tag 'kvmarm-fixes-5.8-3' of git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm into kvm-master (2020-07-06 13:05:38 -0400)
----------------------------------------------------------------
Bugfixes and a one-liner patch to silence sparse.
----------------------------------------------------------------
I'm going on vacation so my next pull request should be for rc8
or 5.8-final. If something really bad comes up, you might get
KVM changes straight from architecture maintainers, but things
seems calm on both the 5.7 and 5.8 fronts so that should not
happen.
Thanks,
Paolo
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
Andrew Scull (1):
KVM: arm64: Stop clobbering x0 for HVC_SOFT_RESTART
Christian Borntraeger (1):
KVM: s390: reduce number of IO pins to 1
Marc Zyngier (2):
KVM: arm64: vgic-v4: Plug race between non-residency and v4.1 doorbell
KVM: arm64: PMU: Fix per-CPU access in preemptible context
Paolo Bonzini (5):
Merge tag 'kvm-s390-master-5.8-3' of git://git.kernel.org/.../kvms390/linux into kvm-master
KVM: x86: bit 8 of non-leaf PDPEs is not reserved
Merge tag 'kvmarm-fixes-5.8-2' of git://git.kernel.org/.../kvmarm/kvmarm into kvm-master
kvm: use more precise cast and do not drop __user
Merge tag 'kvmarm-fixes-5.8-3' of git://git.kernel.org/.../kvmarm/kvmarm into kvm-master
Sean Christopherson (3):
KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode
KVM: x86: Mark CR4.TSD as being possibly owned by the guest
KVM: VMX: Use KVM_POSSIBLE_CR*_GUEST_BITS to initialize guest/host masks
Steven Price (1):
KVM: arm64: Fix kvm_reset_vcpu() return code being incorrect with SVE
Wanpeng Li (1):
KVM: X86: Fix async pf caused null-ptr-deref
arch/arm64/include/asm/arch_gicv3.h | 2 +-
arch/arm64/include/asm/cpufeature.h | 2 +-
arch/arm64/kvm/hyp-init.S | 11 +++++++----
arch/arm64/kvm/pmu.c | 7 ++++++-
arch/arm64/kvm/pvtime.c | 15 ++++++++++++---
arch/arm64/kvm/reset.c | 10 +++++++---
arch/arm64/kvm/vgic/vgic-v4.c | 8 ++++++++
arch/s390/include/asm/kvm_host.h | 8 ++++----
arch/x86/kvm/kvm_cache_regs.h | 2 +-
arch/x86/kvm/mmu/mmu.c | 2 +-
arch/x86/kvm/vmx/nested.c | 4 ++--
arch/x86/kvm/vmx/vmx.c | 13 +++++--------
arch/x86/kvm/x86.c | 5 +++++
drivers/irqchip/irq-gic-v3-its.c | 8 ++++++++
virt/kvm/kvm_main.c | 3 ++-
15 files changed, 70 insertions(+), 30 deletions(-)
next reply other threads:[~2020-07-06 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 17:15 Paolo Bonzini [this message]
2020-07-06 21:45 ` [GIT PULL] KVM changes for Linux 5.8-rc5 pr-tracker-bot
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=20200706171523.12441-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).