From: James Morse <james.morse@arm.com>
To: AKASHI Takahiro <takahiro.akashi@linaro.org>
Cc: mark.rutland@arm.com, geoff@infradead.org,
catalin.marinas@arm.com, will.deacon@arm.com,
marc.zyngier@arm.com, broonie@kernel.org,
david.griego@linaro.org, kexec@lists.infradead.org,
christoffer.dall@linaro.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] fixup! arm64: kvm: allows kvm cpu hotplug
Date: Tue, 20 Oct 2015 17:22:04 +0100 [thread overview]
Message-ID: <56266A2C.7000005@arm.com> (raw)
In-Reply-To: <1445327907-23274-3-git-send-email-takahiro.akashi@linaro.org>
On 20/10/15 08:58, AKASHI Takahiro wrote:
> Without this patch, kvm cannot start a guest when cpuidle is enabled
> if the hardware does not retain cpu state (EL2) in idle state.
>
> This patch re-initailizes EL2 state at CPU_PM_EXIT by calling
> kvm_arch_hardware_enable() if and only if kvm has been initialized
> before CPU_PM_ENTER, that is, if any vcpus have been created.
>
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
This solves my issue with the v5 version here [0].
Tested-By: James Morse <james.morse@arm.com>
Thanks!
James
[0] https://lists.linaro.org/pipermail/linaro-kernel/2015-May/021575.html
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-10-20 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 7:58 [PATCH 0/2] arm64: kexec/kdump fixes for v10 AKASHI Takahiro
2015-10-20 7:58 ` [PATCH 1/2] fixup! arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2015-10-20 7:58 ` [PATCH 2/2] fixup! arm64: kvm: allows kvm cpu hotplug AKASHI Takahiro
2015-10-20 16:22 ` James Morse [this message]
2015-10-20 19:05 ` [PATCH 0/2] arm64: kexec/kdump fixes for v10 Geoff Levand
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=56266A2C.7000005@arm.com \
--to=james.morse@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=david.griego@linaro.org \
--cc=geoff@infradead.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=takahiro.akashi@linaro.org \
--cc=will.deacon@arm.com \
/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