From: Greg KH <gregkh@linuxfoundation.org>
To: Shannon Zhao <shannon.zhao@linaro.org>
Cc: stable@vger.kernel.org, Christoffer Dall <christoffer.dall@linaro.org>
Subject: Re: [PATCH for 3.14.y stable] The list of KVM/ARM fixes for 3.14.y stable kernel
Date: Fri, 15 May 2015 16:09:30 -0700 [thread overview]
Message-ID: <20150515230930.GA12102@kroah.com> (raw)
In-Reply-To: <55540142.9090006@linaro.org>
On Thu, May 14, 2015 at 09:58:26AM +0800, Shannon Zhao wrote:
> Hi Greg,
>
> Below are the git commit ids of KVM/ARM fixes that should be applied to
> the 3.14-stable kernel tree from top to buttom order.
>
> 2d58b73 arm64: KVM: force cache clean on page fault when caches are off
> 2072d29 arm64: KVM: allows discrimination of AArch32 sysreg access
> 4d44923 arm64: KVM: trap VM system registers until MMU and caches are ON
> a3c8bd3 ARM: KVM: introduce kvm_p*d_addr_end
> 9d218a1 arm64: KVM: flush VM pages before letting the guest enable caches
> 1597930 ARM: KVM: force cache clean on page fault when caches are off
> 46c214d ARM: KVM: fix handling of trapped 64bit coprocessor accesses
> 547f781 ARM: KVM: fix ordering of 64bit coprocessor accesses
> ac30a11 ARM: KVM: introduce per-vcpu HYP Configuration Register
> af20814 ARM: KVM: add world-switch for AMAIR{0,1}
> 8034699 ARM: KVM: trap VM system registers until MMU and caches are ON
> f2ae85b KVM: arm/arm64: vgic: fix GICD_ICFGR register accesses
> 30c2117 KVM: ARM: vgic: Fix the overlap check action about setting the GICD & GICC base address.
> ee9e101 arm64: kvm: use inner-shareable barriers for inner-shareable maintenance
> 63afbe7 kvm: arm64: vgic: fix hyp panic with 64k pages on juno platform
> 4f853a7 arm/arm64: KVM: Fix and refactor unmap_range
I've stopped applying things at this point in time, as this commit, as
you mention, doesn't apply cleanly.
Can you provide a working backport of it?
Or better yet, a backport of the ones that you know I will need?
I'll go do the next 3.14-rc release with the above patches included, so
if you could resend the list of what I haven't applied so far, that
would be great.
thanks,
greg k-h
next prev parent reply other threads:[~2015-05-15 23:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 1:58 [PATCH for 3.14.y stable] The list of KVM/ARM fixes for 3.14.y stable kernel Shannon Zhao
2015-05-15 23:09 ` Greg KH [this message]
2015-05-18 1:02 ` Shannon Zhao
2015-06-02 6:37 ` Greg KH
2015-06-02 7:53 ` Shannon Zhao
2015-06-02 9:08 ` Christoffer Dall
2015-06-02 12:56 ` Greg KH
2015-06-02 13:04 ` Shannon Zhao
2015-05-18 13:32 ` Luis Henriques
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=20150515230930.GA12102@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=christoffer.dall@linaro.org \
--cc=shannon.zhao@linaro.org \
--cc=stable@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.