From: julien.grall@linaro.org (Julien Grall)
To: linux-arm-kernel@lists.infradead.org
Subject: [Xen-devel] [PATCH] xen/arm: disable cpuidle when linux is running as dom0
Date: Mon, 15 Jul 2013 17:22:00 +0100 [thread overview]
Message-ID: <51E421A8.1010302@linaro.org> (raw)
In-Reply-To: <20130715152532.GC5774@phenom.dumpdata.com>
On 07/15/2013 04:25 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 03:21:41PM +0100, Julien Grall wrote:
>> When linux is running as dom0, Xen doesn't show the physical cpu but a
>> virtual CPU.
>> On some ARM SOC (for instance the exynos 5250), linux registers callbacks
>> for cpuidle. When these callbacks are called, they will modify
>> directly the physical cpu not the virtual one. It can impact the whole board
>> instead of dom0.
>
> Should you also call disable_cpufreq() ?
I had some issue on the versatile express when cpufreq was disabled.
I will give another try and see the exact error.
--
Julien
WARNING: multiple messages have this Message-ID (diff)
From: Julien Grall <julien.grall@linaro.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: stefano.stabellini@eu.citrix.com, ian.campbell@citrix.com,
patches@linaro.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xen.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [Xen-devel] [PATCH] xen/arm: disable cpuidle when linux is running as dom0
Date: Mon, 15 Jul 2013 17:22:00 +0100 [thread overview]
Message-ID: <51E421A8.1010302@linaro.org> (raw)
In-Reply-To: <20130715152532.GC5774@phenom.dumpdata.com>
On 07/15/2013 04:25 PM, Konrad Rzeszutek Wilk wrote:
> On Mon, Jul 15, 2013 at 03:21:41PM +0100, Julien Grall wrote:
>> When linux is running as dom0, Xen doesn't show the physical cpu but a
>> virtual CPU.
>> On some ARM SOC (for instance the exynos 5250), linux registers callbacks
>> for cpuidle. When these callbacks are called, they will modify
>> directly the physical cpu not the virtual one. It can impact the whole board
>> instead of dom0.
>
> Should you also call disable_cpufreq() ?
I had some issue on the versatile express when cpufreq was disabled.
I will give another try and see the exact error.
--
Julien
next prev parent reply other threads:[~2013-07-15 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 14:21 [PATCH] xen/arm: disable cpuidle when linux is running as dom0 Julien Grall
2013-07-15 14:21 ` Julien Grall
2013-07-15 15:25 ` [Xen-devel] " Konrad Rzeszutek Wilk
2013-07-15 15:25 ` Konrad Rzeszutek Wilk
2013-07-15 16:22 ` Julien Grall [this message]
2013-07-15 16:22 ` Julien Grall
2013-07-15 16:22 ` Julien Grall
2013-07-17 13:28 ` Stefano Stabellini
2013-07-17 13:28 ` [Xen-devel] " Stefano Stabellini
2013-07-17 13:28 ` Stefano Stabellini
2013-07-18 17:20 ` Julien Grall
2013-07-18 17:20 ` Julien Grall
2013-07-18 17:20 ` Julien Grall
2013-07-15 15:25 ` Konrad Rzeszutek Wilk
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=51E421A8.1010302@linaro.org \
--to=julien.grall@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 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.