linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pbonzini@redhat.com (Paolo Bonzini)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] KVM/ARM Urgent fix for 3.16
Date: Wed, 30 Jul 2014 15:34:11 +0200	[thread overview]
Message-ID: <53D8F453.9010101@redhat.com> (raw)
In-Reply-To: <1406724941-4283-1-git-send-email-christoffer.dall@linaro.org>

Il 30/07/2014 14:55, Christoffer Dall ha scritto:
> Hi Paolo and Gleb,
> 
> Is there any chance you can get this urgent fix (which allows KVM guest
> to bring down the entire system on some 64K enabled ARM64 hosts) merged
> for 3.16?
> 
> The following changes since commit bb18b526a9d8d4a3fe56f234d5013b9f6036978d:
> 
>   Merge tag 'signed-for-3.16' of git://github.com/agraf/linux-2.6 into kvm-master (2014-07-08 12:08:58 +0200)
> 
> are available in the git repository at:
> 
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvm-arm-for-3.16-rc7
> 
> for you to fetch changes up to 63afbe7a0ac184ef8485dac4914e87b211b5bfaa:
> 
>   kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform (2014-07-30 14:35:42 +0200)
> 
> ---
> Will Deacon (1):
>   kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform
> 
>  virt/kvm/arm/vgic.c | 24 ++++++++++++++++++++----
>  1 file changed, 20 insertions(+), 4 deletions(-)
> 

I think Gleb is on vacation now, but unfortunately I've already had
enough this year.

I resent the pull request from
git://git.kernel.org/pub/scm/virt/kvm/kvm.git, even though you had CCed
Linus here already.


Paolo

  parent reply	other threads:[~2014-07-30 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-30 12:55 [GIT PULL] KVM/ARM Urgent fix for 3.16 Christoffer Dall
2014-07-30 12:55 ` [PATCH] kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform Christoffer Dall
2014-07-30 13:34 ` Paolo Bonzini [this message]
2014-07-30 18:54   ` [GIT PULL] KVM/ARM Urgent fix for 3.16 Christoffer Dall

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=53D8F453.9010101@redhat.com \
    --to=pbonzini@redhat.com \
    --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 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).