From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] Improve PSCI system events and fix reboot bugs
Date: Tue, 2 Dec 2014 15:47:45 +0100 [thread overview]
Message-ID: <20141202144745.GI545@cbox> (raw)
In-Reply-To: <20141201133411.GA5953@hawk.usersys.redhat.com>
On Mon, Dec 01, 2014 at 02:34:12PM +0100, Andrew Jones wrote:
> On Thu, Nov 27, 2014 at 07:40:55PM +0100, Christoffer Dall wrote:
> > Several people have reported problems with rebooting ARM VMs, especially
> > on 32-bit ARM. This is mainly due to the same reason we were seeing
> > boot errors in the past, namely that the ram, dcache, and icache weren't
> > coherent on guest boot with the guest (stage-1) MMU disabled. We solved
> > this by ensuring coherency when we fault in pages, but since most memory
> > is already mapped after a reboot, we don't do anything.
> >
> > The solution is to unmap the regular RAM on system events, but we must
> > take care to not unmap the GIC or other IO regions, hence the somehwat
> > complicated solution.
> >
> > As part of figuring this out, it became clear that some semantics around
> > the KVM_ARM_VCPU_INIT ABI and system event ABI was unclear (what is
> > userspace expected to do when it receives a system event). This series
> > also clarifies the ABI and changes the kernel functionality to do what
> > userspace expects (turn off VCPUs on a system shutdown event).
> >
> > The code is avaliable here as well:
> > http://git.linaro.org/people/christoffer.dall/linux-kvm-arm.git vcpu_init_fixes
> >
> > There is an alternative version with more code reuse for what is patch 4
> > in this series available here:
> > http://git.linaro.org/people/christoffer.dall/linux-kvm-arm.git vcpu_init_fixes-alternative
> >
> > See patch 4 for more info on this one.
> >
> > Testing
> > -------
> > This has been tested on CubieBoard, Arndale, TC2, and Juno. On Arndale
> > and TC2 it was extremely easy to reproduce the setup (just start a VM
> > that runs reboot from /etc/rc.local or similar) and this series clearly
> > fixes the behavior.
>
> We've also seen reboots leading to a stuck vcpu. It appeared to be 100%
> reproducible on a freshly installed guest (first reboot after running
> the installer), and then intermittently afterwards. I've just tested
> this patch series, and it appears to resolve the issue. No stuck vcpu
> after install, and a reboot loop has been running for a while now. I'm
> testing on a mustang. If you like, feel free to add a
>
> Tested-by: Andrew Jones <drjones@redhat.com>
>
Thanks!
-Christoffer
prev parent reply other threads:[~2014-12-02 14:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 18:40 [PATCH 0/5] Improve PSCI system events and fix reboot bugs Christoffer Dall
2014-11-27 18:40 ` [PATCH 1/5] arm/arm64: KVM: Correct KVM_ARM_VCPU_INIT power off option Christoffer Dall
2014-11-27 22:44 ` Peter Maydell
2014-12-02 14:33 ` Christoffer Dall
2014-11-27 18:40 ` [PATCH 2/5] arm/arm64: KVM: Reset the HCR on each vcpu when resetting the vcpu Christoffer Dall
2014-11-27 18:40 ` [PATCH 3/5] arm/arm64: KVM: Clarify KVM_ARM_VCPU_INIT ABI Christoffer Dall
2014-11-27 22:53 ` Peter Maydell
2014-12-02 14:47 ` Christoffer Dall
2014-12-02 15:39 ` Peter Maydell
2014-12-02 19:02 ` Christoffer Dall
2014-11-27 18:40 ` [PATCH 4/5] arm/arm64: KVM: Introduce stage2_unmap_vm Christoffer Dall
2014-11-27 18:41 ` [PATCH 5/5] arm/arm64: KVM: Turn off vcpus and flush stage-2 pgtables on sytem exit events Christoffer Dall
2014-11-27 23:10 ` Peter Maydell
2014-12-01 17:57 ` Peter Maydell
2014-12-02 13:29 ` Christoffer Dall
2014-12-02 15:01 ` Christoffer Dall
2014-12-02 15:42 ` Peter Maydell
2014-12-01 13:34 ` [PATCH 0/5] Improve PSCI system events and fix reboot bugs Andrew Jones
2014-12-02 14:47 ` Christoffer Dall [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=20141202144745.GI545@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 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).