From: Krzysztof Kozlowski <krzk@kernel.org>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: Shannon Zhao <shannon.zhao@linaro.org>,
Igor Mitsyanko <i.mitsyanko@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Subject: [Qemu-devel] [RFC 0/5] hw: arm: exynos: Bring up secondary CPU + CPUIDLE issue
Date: Wed, 1 Mar 2017 20:26:13 +0200 [thread overview]
Message-ID: <20170301182618.22395-1-krzk@kernel.org> (raw)
Hi,
The first patch fixes GIC and brings the secondary CPU. Unfortunately,
this brings up to light an annoying issue with CPUIDLE driver.
Overview of the problem
=======================
On Exynos4210, by default Linux kernel uses cpuidle driver which tries
to enter low power mode, called AFTR (Arm Off, Top Running). On real
hardware this brings some power savings. This AFTR mode requires second
CPU to be off, so the driver (coupled cpuidle driver) when system is idle:
1. Turns off second CPU,
2. Enters AFTR on CPU0.
However the QEMU system is then totally unresponsive (e.g. on serial console)
and RCU stalls appear from time to time. I spent some time on it and did not
find the real cause behind the lag. Maybe it is because the second CPU
does not really power down itself and system just burns the cycles under spin
locks?
Looking at recent stable kernels:
- 3.10, 3.16 - works fine with two CPUs (no CPUIDLE driver),
- 4.1 and newer - stalls and are unresponsive due to CPUIDLE being enabled.
The cpuidle driver is not relying on DTS. It is just enabled in exynos_defconfig
and works.
Question
========
I am quite new to QEMU. I do not know the internals (yet), nor the design
how hardware should be emulated in such subtle details.
The questions I have are:
1. What is the preferred way to solve it? Maybe some a QEMU
workaround to disable the cpuidle is okay?
2. Is it worth implementing a proper secondary CPU power down and
at the end proper AFTR cpuidle? It might be quite difficult...
3. How such issues with deep sleep modes were solved for other
ARM targets?
Best regards,
Krzysztof
Krzysztof Kozlowski (5):
hw/intc/exynos4210_gic: Fix GIC memory mappings for secondary CPU
hw/intc/exynos4210_gic: Use more meaningful name for local variable
hw/timer/exynos4210_mct: Cleanup indentation and empty new lines
hw/timer/exynos4210_mct: Fix checkpatch style errors
hw/timer/exynos4210_mct: Remove unused defines
hw/intc/exynos4210_gic.c | 36 ++++++++++++++++++++--------------
hw/timer/exynos4210_mct.c | 50 ++++++++++++++++++++---------------------------
2 files changed, 42 insertions(+), 44 deletions(-)
--
2.9.3
next reply other threads:[~2017-03-01 18:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 18:26 Krzysztof Kozlowski [this message]
2017-03-01 18:26 ` [Qemu-devel] [PATCH 1/5] hw/intc/exynos4210_gic: Fix GIC memory mappings for secondary CPU Krzysztof Kozlowski
2017-03-02 16:37 ` Peter Maydell
2017-03-02 16:50 ` Krzysztof Kozlowski
2017-03-01 18:26 ` [Qemu-devel] [PATCH 2/5] hw/intc/exynos4210_gic: Use more meaningful name for local variable Krzysztof Kozlowski
2017-03-02 16:37 ` Peter Maydell
2017-03-01 18:26 ` [Qemu-devel] [PATCH 3/5] hw/timer/exynos4210_mct: Cleanup indentation and empty new lines Krzysztof Kozlowski
2017-03-02 16:39 ` Peter Maydell
2017-03-01 18:26 ` [Qemu-devel] [PATCH 4/5] hw/timer/exynos4210_mct: Fix checkpatch style errors Krzysztof Kozlowski
2017-03-02 16:40 ` Peter Maydell
2017-03-02 16:44 ` Peter Maydell
2017-03-02 16:48 ` Krzysztof Kozlowski
2017-03-01 18:26 ` [Qemu-devel] [PATCH 5/5] hw/timer/exynos4210_mct: Remove unused defines Krzysztof Kozlowski
2017-03-02 16:40 ` Peter Maydell
2017-03-01 18:33 ` [Qemu-devel] [RFC 0/5] hw: arm: exynos: Bring up secondary CPU + CPUIDLE issue no-reply
2017-03-02 16:56 ` Peter Maydell
2017-03-05 18:52 ` Krzysztof Kozlowski
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=20170301182618.22395-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=i.mitsyanko@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.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).