From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: mingo@kernel.org, linux-kernel@vger.kernel.org,
tony.luck@intel.com, fenghua.yu@intel.com,
schwidefsky@de.ibm.com, cmetcalf@tilera.com,
benh@kernel.crashing.org, linux@arm.linux.org.uk,
linux-arm-kernel@lists.infradead.org, dietmar.eggemann@arm.com,
preeti@linux.vnet.ibm.com, linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v4 4/5] sched: add a new SD_SHARE_POWERDOMAIN for sched_domain
Date: Fri, 18 Apr 2014 12:58:01 +0200 [thread overview]
Message-ID: <20140418105801.GV11182@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1397209481-28542-5-git-send-email-vincent.guittot@linaro.org>
On Fri, Apr 11, 2014 at 11:44:40AM +0200, Vincent Guittot wrote:
> A new flag SD_SHARE_POWERDOMAIN is created to reflect whether groups of CPUs
> in a sched_domain level can or not reach different power state. As an example,
> the flag should be cleared at CPU level if groups of cores can be power gated
> independently. This information can be used in the load balance decision or to
> add load balancing level between group of CPUs that can power gate
> independantly.
> This flag is part of the topology flags that can be set by arch.
>
> Signed-off-by: Vincent Guittot <vincent.guittot@linaro.org>
> ---
Building a cris-defconfig this gets me an endless stream of misery:
In file included from /usr/src/linux-2.6/init/do_mounts.c:12:0:
/usr/src/linux-2.6/include/linux/sched.h:1048:46: warning: 'struct sched_domain_topology_level' declared inside parameter list [enabled by default]
/usr/src/linux-2.6/include/linux/sched.h:1048:46: warning: its scope is only this definition or declaration, which is probably not what you want [enabled by default]
In file included from /usr/src/linux-2.6/include/linux/utsname.h:5:0,
from /usr/src/linux-2.6/include/linux/init_task.h:6,
from /usr/src/linux-2.6/init/init_task.c:1:
Might be something about UP builds, didn't check x86-UP.
next prev parent reply other threads:[~2014-04-18 10:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 9:44 [PATCH v4 0/5] rework sched_domain topology description Vincent Guittot
2014-04-11 9:44 ` [PATCH v4 1/5] sched: rework of sched_domain topology definition Vincent Guittot
2014-04-18 10:56 ` Peter Zijlstra
2014-04-18 11:34 ` [PATCH] fix: " Vincent Guittot
2014-04-18 11:39 ` Peter Zijlstra
2014-04-18 11:34 ` [PATCH v4 1/5] " Vincent Guittot
2014-05-08 10:43 ` [tip:sched/core] sched: Rework " tip-bot for Vincent Guittot
2014-05-16 9:57 ` James Hogan
2014-05-18 8:04 ` Vincent Guittot
2014-04-11 9:44 ` [PATCH v4 2/5] sched: s390: create a dedicated topology table Vincent Guittot
2014-05-08 10:43 ` [tip:sched/core] sched, s390: Create " tip-bot for Vincent Guittot
2014-04-11 9:44 ` [PATCH v4 3/5] sched: powerpc: create " Vincent Guittot
2014-05-08 10:43 ` [tip:sched/core] sched, powerpc: Create " tip-bot for Vincent Guittot
2014-04-11 9:44 ` [PATCH v4 4/5] sched: add a new SD_SHARE_POWERDOMAIN for sched_domain Vincent Guittot
2014-04-18 10:58 ` Peter Zijlstra [this message]
2014-04-18 11:54 ` [PATCH] fix: sched: rework of sched_domain topology definition Vincent Guittot
2014-04-18 11:54 ` [PATCH v4 4/5] sched: add a new SD_SHARE_POWERDOMAIN for sched_domain Vincent Guittot
2014-05-08 10:44 ` [tip:sched/core] sched: Add " tip-bot for Vincent Guittot
2014-04-11 9:44 ` [PATCH v4 5/5] sched: ARM: create a dedicated scheduler topology table Vincent Guittot
2014-04-23 11:46 ` Dietmar Eggemann
2014-04-23 14:46 ` Vincent Guittot
2014-04-23 15:26 ` Dietmar Eggemann
2014-04-24 7:30 ` Vincent Guittot
2014-04-24 12:48 ` Dietmar Eggemann
2014-04-25 7:45 ` Vincent Guittot
2014-04-25 15:55 ` Dietmar Eggemann
2014-04-25 16:04 ` Peter Zijlstra
2014-04-25 16:05 ` Peter Zijlstra
2014-05-08 10:44 ` [tip:sched/core] sched, ARM: Create " tip-bot for Vincent Guittot
2014-04-12 12:56 ` [PATCH v4 0/5] rework sched_domain topology description Dietmar Eggemann
2014-04-14 7:29 ` Vincent Guittot
2014-04-15 7:53 ` Peter Zijlstra
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=20140418105801.GV11182@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=cmetcalf@tilera.com \
--cc=dietmar.eggemann@arm.com \
--cc=fenghua.yu@intel.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@kernel.org \
--cc=preeti@linux.vnet.ibm.com \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=vincent.guittot@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