From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org,
"kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>
Subject: Re: [PULL 0/7] ppc patch queue 2013-06-30
Date: Tue, 02 Jul 2013 07:47:40 +0000 [thread overview]
Message-ID: <51D2859C.9010006@redhat.com> (raw)
In-Reply-To: <1372556328-18617-1-git-send-email-agraf@suse.de>
Il 30/06/2013 03:38, Alexander Graf ha scritto:
> Hi Marcelo / Gleb,
>
> This is my current patch queue for ppc. Please pull and apply to next, so it
> makes its way into 3.11.
>
> Changes include:
>
> - Book3S PR: Add support for 1TB segments
> - Book3S PR fixes
>
> Alex
>
>
> The following changes since commit 96f7edf9a54ca834f030ddf30f91750b3d737a03:
>
> Merge git://git.linaro.org/people/cdall/linux-kvm-arm.git tags/kvm-arm-3.11 into queue (2013-06-27 14:20:54 +0300)
>
> are available in the git repository at:
>
>
> git://github.com/agraf/linux-2.6.git kvm-ppc-queue
>
> for you to fetch changes up to a3ff5fbc94a829680d4aa005cd17add1c1a1fb5b:
>
> KVM: PPC: Ignore PIR writes (2013-06-30 03:33:22 +0200)
>
> ----------------------------------------------------------------
> Alexander Graf (1):
> KVM: PPC: Ignore PIR writes
>
> Paul Mackerras (5):
> KVM: PPC: Book3S PR: Fix proto-VSID calculations
> KVM: PPC: Book3S PR: Fix invalidation of SLB entry 0 on guest entry
> KVM: PPC: Book3S PR: Don't keep scanning HPTEG after we find a match
> KVM: PPC: Book3S PR: Allow guest to use 1TB segments
> KVM: PPC: Book3S PR: Invalidate SLB entries properly
>
> Tiejun Chen (1):
> KVM: PPC: Guard doorbell exception with CONFIG_PPC_DOORBELL
>
> arch/powerpc/include/asm/kvm_book3s.h | 6 ++-
> arch/powerpc/kvm/book3s_64_mmu.c | 81 ++++++++++++++++++++++-------------
> arch/powerpc/kvm/book3s_64_mmu_host.c | 21 ++++++++-
> arch/powerpc/kvm/book3s_64_slb.S | 13 +-----
> arch/powerpc/kvm/book3s_pr.c | 3 +-
> arch/powerpc/kvm/booke.c | 2 +-
> arch/powerpc/kvm/emulate.c | 3 ++
> 7 files changed, 82 insertions(+), 47 deletions(-)
>
Pulled, thanks!
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org,
"kvm@vger.kernel.org mailing list" <kvm@vger.kernel.org>
Subject: Re: [PULL 0/7] ppc patch queue 2013-06-30
Date: Tue, 02 Jul 2013 09:47:40 +0200 [thread overview]
Message-ID: <51D2859C.9010006@redhat.com> (raw)
In-Reply-To: <1372556328-18617-1-git-send-email-agraf@suse.de>
Il 30/06/2013 03:38, Alexander Graf ha scritto:
> Hi Marcelo / Gleb,
>
> This is my current patch queue for ppc. Please pull and apply to next, so it
> makes its way into 3.11.
>
> Changes include:
>
> - Book3S PR: Add support for 1TB segments
> - Book3S PR fixes
>
> Alex
>
>
> The following changes since commit 96f7edf9a54ca834f030ddf30f91750b3d737a03:
>
> Merge git://git.linaro.org/people/cdall/linux-kvm-arm.git tags/kvm-arm-3.11 into queue (2013-06-27 14:20:54 +0300)
>
> are available in the git repository at:
>
>
> git://github.com/agraf/linux-2.6.git kvm-ppc-queue
>
> for you to fetch changes up to a3ff5fbc94a829680d4aa005cd17add1c1a1fb5b:
>
> KVM: PPC: Ignore PIR writes (2013-06-30 03:33:22 +0200)
>
> ----------------------------------------------------------------
> Alexander Graf (1):
> KVM: PPC: Ignore PIR writes
>
> Paul Mackerras (5):
> KVM: PPC: Book3S PR: Fix proto-VSID calculations
> KVM: PPC: Book3S PR: Fix invalidation of SLB entry 0 on guest entry
> KVM: PPC: Book3S PR: Don't keep scanning HPTEG after we find a match
> KVM: PPC: Book3S PR: Allow guest to use 1TB segments
> KVM: PPC: Book3S PR: Invalidate SLB entries properly
>
> Tiejun Chen (1):
> KVM: PPC: Guard doorbell exception with CONFIG_PPC_DOORBELL
>
> arch/powerpc/include/asm/kvm_book3s.h | 6 ++-
> arch/powerpc/kvm/book3s_64_mmu.c | 81 ++++++++++++++++++++++-------------
> arch/powerpc/kvm/book3s_64_mmu_host.c | 21 ++++++++-
> arch/powerpc/kvm/book3s_64_slb.S | 13 +-----
> arch/powerpc/kvm/book3s_pr.c | 3 +-
> arch/powerpc/kvm/booke.c | 2 +-
> arch/powerpc/kvm/emulate.c | 3 ++
> 7 files changed, 82 insertions(+), 47 deletions(-)
>
Pulled, thanks!
Paolo
next prev parent reply other threads:[~2013-07-02 7:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-30 1:38 [PULL 0/7] ppc patch queue 2013-06-30 Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 1/7] KVM: PPC: Guard doorbell exception with CONFIG_PPC_DOORBELL Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 2/7] KVM: PPC: Book3S PR: Fix proto-VSID calculations Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 3/7] KVM: PPC: Book3S PR: Fix invalidation of SLB entry 0 on guest entry Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 4/7] KVM: PPC: Book3S PR: Don't keep scanning HPTEG after we find a match Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 5/7] KVM: PPC: Book3S PR: Allow guest to use 1TB segments Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 6/7] KVM: PPC: Book3S PR: Invalidate SLB entries properly Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:38 ` [PATCH 7/7] KVM: PPC: Ignore PIR writes Alexander Graf
2013-06-30 1:38 ` Alexander Graf
2013-06-30 1:59 ` [PULL 0/7] ppc patch queue 2013-06-30 Alexander Graf
2013-06-30 1:59 ` Alexander Graf
2013-07-02 7:47 ` Paolo Bonzini [this message]
2013-07-02 7:47 ` 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=51D2859C.9010006@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.