From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 0/9] KVM/ARM Changes for v3.19
Date: Thu, 11 Dec 2014 13:02:59 +0100 [thread overview]
Message-ID: <20141211120259.GH28388@cbox> (raw)
In-Reply-To: <548985F6.4030905@redhat.com>
On Thu, Dec 11, 2014 at 12:54:30PM +0100, Paolo Bonzini wrote:
>
>
> On 11/12/2014 10:47, Christoffer Dall wrote:
> > On Tue, Dec 09, 2014 at 08:39:39PM +0100, Paolo Bonzini wrote:
> >>
> >>
> >> On 09/12/2014 12:25, Christoffer Dall wrote:
> >>> Hi Paolo,
> >>>
> >>> The following changes since commit f62c95fd4041d669159dd76ac0bb2a7f86b5b05d:
> >>>
> >>> Merge tag 'kvm-s390-next-20141028' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2014-10-29 13:31:32 +0100)
> >>>
> >>> are available in the git repository at:
> >>>
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git kvm-arm-for-3.19
> >>>
> >>> for you to fetch changes up to 016ed39c54b8a3db680e5c6a43419f806133caf2:
> >>>
> >>> arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating through all (2014-11-26 10:19:37 +0000)
> >>>
> >>> Thanks,
> >>> -Christoffer
> >>>
> >>> ----------------------------------------------------------------
> >>> Changes for KVM for arm/arm64 for v3.19 including mmio mapping fixups
> >>> (already in kvm/next, apologies about duplicate commits), vgic cleanup
> >>> and optimizations, and an MMIO path cleanup.
> >>>
> >>> ----------------------------------------------------------------
> >>>
> >>>
> >>> Andre Przywara (1):
> >>> arm/arm64: KVM: avoid unnecessary guest register mangling on MMIO read
> >>>
> >>> Ard Biesheuvel (4):
> >>> arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn()
> >>> kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn()
> >>> kvm: add a memslot flag for incoherent memory regions
> >>> arm, arm64: KVM: handle potential incoherency of readonly memslots
> >>>
> >>> Christoffer Dall (1):
> >>> arm/arm64: vgic: Remove unreachable irq_clear_pending
> >>>
> >>> Laszlo Ersek (1):
> >>> arm, arm64: KVM: allow forced dcache flush on page faults
> >>>
> >>> Shannon Zhao (1):
> >>> arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating
> >>> through all
> >>>
> >>> wanghaibin (1):
> >>> KVM: ARM: VGIC: Optimize the vGIC vgic_update_irq_pending function.
> >>>
> >>> arch/arm/include/asm/kvm_mmu.h | 5 +++--
> >>> arch/arm/kvm/mmio.c | 15 +++++++++------
> >>> arch/arm/kvm/mmu.c | 34 +++++++++++++++++++++++++++-------
> >>> arch/arm64/include/asm/kvm_mmu.h | 5 +++--
> >>> arch/ia64/kvm/kvm-ia64.c | 2 +-
> >>> arch/x86/kvm/mmu.c | 6 +++---
> >>> include/linux/kvm_host.h | 3 ++-
> >>> virt/kvm/arm/vgic.c | 20 +++++++++++++-------
> >>> virt/kvm/kvm_main.c | 16 ++++++++--------
> >>> 9 files changed, 69 insertions(+), 37 deletions(-)
> >>>
> >>
> >> No dirty bitmap yet? You still have one week, I'm okay with a late
> >> addition.
> >>
> > No, we spotted a bug in the last revision and I prefer not merging it at
> > this short notice, because I won't have proper time to test the stuff.
> >
> > The plan is to put it in kvmarm/next right after the merge window
> > closes.
>
> Since there are x86 bits, please send an "unusual" kvmarm/next pull
> request as soon as it's ready. This way the 3.20 kvm/next and
> kvmarm/next trees can both include it.
>
Yes, that's what I meant actually, we'd put it in kvm/arm next as soon
as you've rebased kvm/next and send a pull request immediately, sorry
for being unclear.
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [GIT PULL 0/9] KVM/ARM Changes for v3.19
Date: Thu, 11 Dec 2014 13:02:59 +0100 [thread overview]
Message-ID: <20141211120259.GH28388@cbox> (raw)
In-Reply-To: <548985F6.4030905@redhat.com>
On Thu, Dec 11, 2014 at 12:54:30PM +0100, Paolo Bonzini wrote:
>
>
> On 11/12/2014 10:47, Christoffer Dall wrote:
> > On Tue, Dec 09, 2014 at 08:39:39PM +0100, Paolo Bonzini wrote:
> >>
> >>
> >> On 09/12/2014 12:25, Christoffer Dall wrote:
> >>> Hi Paolo,
> >>>
> >>> The following changes since commit f62c95fd4041d669159dd76ac0bb2a7f86b5b05d:
> >>>
> >>> Merge tag 'kvm-s390-next-20141028' of git://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux into HEAD (2014-10-29 13:31:32 +0100)
> >>>
> >>> are available in the git repository at:
> >>>
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git kvm-arm-for-3.19
> >>>
> >>> for you to fetch changes up to 016ed39c54b8a3db680e5c6a43419f806133caf2:
> >>>
> >>> arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating through all (2014-11-26 10:19:37 +0000)
> >>>
> >>> Thanks,
> >>> -Christoffer
> >>>
> >>> ----------------------------------------------------------------
> >>> Changes for KVM for arm/arm64 for v3.19 including mmio mapping fixups
> >>> (already in kvm/next, apologies about duplicate commits), vgic cleanup
> >>> and optimizations, and an MMIO path cleanup.
> >>>
> >>> ----------------------------------------------------------------
> >>>
> >>>
> >>> Andre Przywara (1):
> >>> arm/arm64: KVM: avoid unnecessary guest register mangling on MMIO read
> >>>
> >>> Ard Biesheuvel (4):
> >>> arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn()
> >>> kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn()
> >>> kvm: add a memslot flag for incoherent memory regions
> >>> arm, arm64: KVM: handle potential incoherency of readonly memslots
> >>>
> >>> Christoffer Dall (1):
> >>> arm/arm64: vgic: Remove unreachable irq_clear_pending
> >>>
> >>> Laszlo Ersek (1):
> >>> arm, arm64: KVM: allow forced dcache flush on page faults
> >>>
> >>> Shannon Zhao (1):
> >>> arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating
> >>> through all
> >>>
> >>> wanghaibin (1):
> >>> KVM: ARM: VGIC: Optimize the vGIC vgic_update_irq_pending function.
> >>>
> >>> arch/arm/include/asm/kvm_mmu.h | 5 +++--
> >>> arch/arm/kvm/mmio.c | 15 +++++++++------
> >>> arch/arm/kvm/mmu.c | 34 +++++++++++++++++++++++++++-------
> >>> arch/arm64/include/asm/kvm_mmu.h | 5 +++--
> >>> arch/ia64/kvm/kvm-ia64.c | 2 +-
> >>> arch/x86/kvm/mmu.c | 6 +++---
> >>> include/linux/kvm_host.h | 3 ++-
> >>> virt/kvm/arm/vgic.c | 20 +++++++++++++-------
> >>> virt/kvm/kvm_main.c | 16 ++++++++--------
> >>> 9 files changed, 69 insertions(+), 37 deletions(-)
> >>>
> >>
> >> No dirty bitmap yet? You still have one week, I'm okay with a late
> >> addition.
> >>
> > No, we spotted a bug in the last revision and I prefer not merging it at
> > this short notice, because I won't have proper time to test the stuff.
> >
> > The plan is to put it in kvmarm/next right after the merge window
> > closes.
>
> Since there are x86 bits, please send an "unusual" kvmarm/next pull
> request as soon as it's ready. This way the 3.20 kvm/next and
> kvmarm/next trees can both include it.
>
Yes, that's what I meant actually, we'd put it in kvm/arm next as soon
as you've rebased kvm/next and send a pull request immediately, sorry
for being unclear.
-Christoffer
next prev parent reply other threads:[~2014-12-11 12:02 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 11:25 [GIT PULL 0/9] KVM/ARM Changes for v3.19 Christoffer Dall
2014-12-09 11:25 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 1/9] KVM: ARM: VGIC: Optimize the vGIC vgic_update_irq_pending function Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 2/9] arm/arm64: kvm: drop inappropriate use of kvm_is_mmio_pfn() Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 12:29 ` Ard Biesheuvel
2014-12-09 12:29 ` Ard Biesheuvel
2014-12-09 12:38 ` Christoffer Dall
2014-12-09 12:38 ` Christoffer Dall
2014-12-09 12:38 ` Ard Biesheuvel
2014-12-09 12:38 ` Ard Biesheuvel
2014-12-09 11:26 ` [GIT PULL 3/9] kvm: fix kvm_is_mmio_pfn() and rename to kvm_is_reserved_pfn() Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 4/9] kvm: add a memslot flag for incoherent memory regions Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 5/9] arm, arm64: KVM: allow forced dcache flush on page faults Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 6/9] arm, arm64: KVM: handle potential incoherency of readonly memslots Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 7/9] arm/arm64: KVM: avoid unnecessary guest register mangling on MMIO read Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 8/9] arm/arm64: vgic: Remove unreachable irq_clear_pending Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 11:26 ` [GIT PULL 9/9] arm/arm64: KVM: vgic: kick the specific vcpu instead of iterating through all Christoffer Dall
2014-12-09 11:26 ` Christoffer Dall
2014-12-09 19:39 ` [GIT PULL 0/9] KVM/ARM Changes for v3.19 Paolo Bonzini
2014-12-09 19:39 ` Paolo Bonzini
2014-12-11 9:47 ` Christoffer Dall
2014-12-11 9:47 ` Christoffer Dall
2014-12-11 11:54 ` Paolo Bonzini
2014-12-11 11:54 ` Paolo Bonzini
2014-12-11 12:02 ` Christoffer Dall [this message]
2014-12-11 12:02 ` Christoffer Dall
2014-12-11 11:52 ` Paolo Bonzini
2014-12-11 11:52 ` Paolo Bonzini
2014-12-11 11:59 ` Christoffer Dall
2014-12-11 11:59 ` Christoffer Dall
2014-12-11 12:04 ` Paolo Bonzini
2014-12-11 12:04 ` 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=20141211120259.GH28388@cbox \
--to=christoffer.dall@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.