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 fixes for 4.4-rc4
Date: Fri, 4 Dec 2015 18:39:08 +0100	[thread overview]
Message-ID: <5661CFBC.3030601@redhat.com> (raw)
In-Reply-To: <1449249440-28878-1-git-send-email-marc.zyngier@arm.com>



On 04/12/2015 18:17, Marc Zyngier wrote:
> Hi Paolo,
> 
> This pull request contains a number of fixes for 4.4-rc4 (or -rc5 if
> we already missed the boat).
> 
> The first part is a very nice catch from Pavel, who noticed that we
> were not dealing very well (if at all) with the aliasing between two
> registers.
> 
> The last patch from Ard is a fix for a fix that was merged in
> -rc3. Hopefully we got it right this time.
> 
> Please pull!
> 
>        M.
> 
> The following changes since commit fbb4574ce9a37e15a9872860bf202f2be5bdf6c4:
> 
>   arm64: kvm: report original PAR_EL1 upon panic (2015-11-24 18:20:58 +0100)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvm-arm-for-v4.4-rc4
> 
> for you to fetch changes up to 0de58f852875a0f0dcfb120bb8433e4e73c7803b:
> 
>   ARM/arm64: KVM: correct PTE uncachedness check (2015-12-04 16:30:17 +0000)
> 
> ----------------------------------------------------------------
> KVM/ARM fixes for v4.4-rc4
> 
> - A series of fixes to deal with the aliasing between the sp and xzr register
> - A fix for the cache flush fix that went in -rc3
> 
> ----------------------------------------------------------------
> Ard Biesheuvel (1):
>       ARM/arm64: KVM: correct PTE uncachedness check
> 
> Pavel Fedin (4):
>       arm64: KVM: Correctly handle zero register during MMIO
>       arm64: KVM: Remove const from struct sys_reg_params
>       arm64: KVM: Correctly handle zero register in system register accesses
>       arm64: KVM: Get rid of old vcpu_reg()
> 
>  arch/arm/include/asm/kvm_emulate.h   |  12 ++++
>  arch/arm/kvm/mmio.c                  |   5 +-
>  arch/arm/kvm/mmu.c                   |   4 +-
>  arch/arm/kvm/psci.c                  |  20 +++---
>  arch/arm64/include/asm/kvm_emulate.h |  18 +++--
>  arch/arm64/kvm/handle_exit.c         |   2 +-
>  arch/arm64/kvm/sys_regs.c            | 123 +++++++++++++++++------------------
>  arch/arm64/kvm/sys_regs.h            |   8 +--
>  arch/arm64/kvm/sys_regs_generic_v8.c |   4 +-
>  9 files changed, 107 insertions(+), 89 deletions(-)
> 

Pulled, thanks.

Paolo

      parent reply	other threads:[~2015-12-04 17:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04 17:17 [GIT PULL] KVM/ARM fixes for 4.4-rc4 Marc Zyngier
2015-12-04 17:17 ` [PATCH 1/5] arm64: KVM: Correctly handle zero register during MMIO Marc Zyngier
2015-12-04 17:17 ` [PATCH 2/5] arm64: KVM: Remove const from struct sys_reg_params Marc Zyngier
2015-12-04 17:17 ` [PATCH 3/5] arm64: KVM: Correctly handle zero register in system register accesses Marc Zyngier
2015-12-04 17:17 ` [PATCH 4/5] arm64: KVM: Get rid of old vcpu_reg() Marc Zyngier
2015-12-04 17:17 ` [PATCH 5/5] ARM/arm64: KVM: correct PTE uncachedness check Marc Zyngier
2015-12-04 17:39 ` Paolo Bonzini [this message]

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=5661CFBC.3030601@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).