[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kvm-ppc
Subject:    Re: [GIT PULL] Please pull my kvm-ppc-next branch
From:       Paolo Bonzini <pbonzini () redhat ! com>
Date:       2016-01-15 16:49:59
Message-ID: 56992337.9020702 () redhat ! com
[Download RAW message or body]



On 15/01/2016 11:35, Paul Mackerras wrote:
> Hi Paolo,
> 
> Please do a pull from my kvm-ppc-next branch to get a PPC update for
> v4.5.  All of these commits have been in linux-next for weeks except
> for the get/set_one_reg fix for Altivec from Greg Kurz, which was in
> linux-next today and is a really simple and obvious fix.
> 
> Thanks,
> Paul.
> 
> The following changes since commit 460146348518a1c4e810d01baf81847f8c6a1c73:
> 
> Merge tag 'kvm-s390-next-4.5-1' of \
> git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2015-12-02 \
> 13:50:04 +0100) 
> are available in the git repository at:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git kvm-ppc-next
> 
> for you to fetch changes up to b4d7f161feb3015d6306e1d35b565c888ff70c9d:
> 
> KVM: PPC: Fix ONE_REG AltiVec support (2016-01-14 14:43:35 +1100)
> 
> ----------------------------------------------------------------
> Geyslan G. Bem (1):
> KVM: PPC: Book3S PR: Remove unused variable 'vcpu_book3s'
> 
> Greg Kurz (1):
> KVM: PPC: Fix ONE_REG AltiVec support
> 
> Paul Mackerras (1):
> KVM: PPC: Book3S HV: Handle unexpected traps in guest entry/exit code better
> 
> Thomas Huth (2):
> KVM: PPC: Fix emulation of H_SET_DABR/X on POWER8
> KVM: PPC: Increase memslots to 512
> 
> arch/powerpc/include/asm/kvm_host.h     |  3 +--
> arch/powerpc/kvm/book3s_64_mmu.c        |  3 ---
> arch/powerpc/kvm/book3s_hv.c            | 18 ++++++++++++++++++
> arch/powerpc/kvm/book3s_hv_rmhandlers.S |  4 +++-
> arch/powerpc/kvm/powerpc.c              | 20 ++++++++++----------
> 5 files changed, 32 insertions(+), 16 deletions(-)
> 

Pulled, thanks.

Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[prev in list] [next in list] [prev in thread] [next in thread]