linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Morten Rasmussen <morten.rasmussen@arm.com>
Cc: mingo@redhat.com, valentin.schneider@arm.com,
	dietmar.eggemann@arm.com, vincent.guittot@linaro.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] sched/topology: Set SD_ASYM_CPUCAPACITY flag automatically
Date: Tue, 31 Jul 2018 12:53:49 +0200	[thread overview]
Message-ID: <20180731105349.GQ2476@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1532093554-30504-1-git-send-email-morten.rasmussen@arm.com>

On Fri, Jul 20, 2018 at 02:32:30PM +0100, Morten Rasmussen wrote:
> The SD_ASYM_CPUCAPACITY flag has been around for some time now with no code to
> actually set it. Android has carried patches to do this out-of-tree in the
> meantime. The flag is meant to indicate cpu capacity asymmetry and is set at
> the topology level where the sched_domain spans all available cpu capacity in
> the system, i.e. all core types are visible, for any cpu in the system.
> 
> The flag was merged as being a topology flag meaning that architecture had to
> provide the flag explicitly, however when mixed with cpusets splitting the
> system into multiple root_domains the flag can't be set without knowledge about
> the cpusets. Rather than exposing cpusets to architecture code this patch set
> moves the responsibility for setting the flag to generic topology code which is
> simpler and make the code architecture agnostic.
> 
> Morten Rasmussen (4):
>   sched/topology: SD_ASYM_CPUCAPACITY flag detection
>   drivers/base/arch_topology: Rebuild sched_domain hierarchy when
>     capacities change
>   arch/arm64: Rebuild sched_domain hierarchy when cpu capacity changes
>   arch/arm: Rebuild sched_domain hierarchy when cpu capacity changes
> 
>  arch/arm/include/asm/topology.h   |  3 ++
>  arch/arm64/include/asm/topology.h |  3 ++
>  drivers/base/arch_topology.c      | 26 +++++++++++++
>  include/linux/arch_topology.h     |  1 +
>  include/linux/sched/topology.h    |  2 +-
>  kernel/sched/topology.c           | 81 ++++++++++++++++++++++++++++++++++++---
>  6 files changed, 109 insertions(+), 7 deletions(-)

I've picked up the lot; Thanks!

      parent reply	other threads:[~2018-07-31 10:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-20 13:32 [PATCH 0/4] sched/topology: Set SD_ASYM_CPUCAPACITY flag automatically Morten Rasmussen
2018-07-20 13:32 ` [PATCH 1/4] sched/topology: SD_ASYM_CPUCAPACITY flag detection Morten Rasmussen
2018-07-23 13:25   ` Qais Yousef
2018-07-23 15:27     ` Morten Rasmussen
2018-07-23 16:07       ` Qais Yousef
2018-07-24  8:37         ` Morten Rasmussen
2018-07-24  8:59           ` Qais Yousef
2018-09-10  8:21   ` Ingo Molnar
2018-09-11 11:04     ` Morten Rasmussen
2018-09-10 10:11   ` [tip:sched/core] sched/topology: Add " tip-bot for Morten Rasmussen
2018-07-20 13:32 ` [PATCH 2/4] drivers/base/arch_topology: Rebuild sched_domain hierarchy when capacities change Morten Rasmussen
2018-09-10 10:11   ` [tip:sched/core] sched/topology, drivers/base/arch_topology: Rebuild the " tip-bot for Morten Rasmussen
2018-07-20 13:32 ` [PATCH 3/4] arch/arm64: Rebuild sched_domain hierarchy when cpu capacity changes Morten Rasmussen
2018-09-10 10:12   ` [tip:sched/core] sched/topology, arch/arm64: Rebuild the sched_domain hierarchy when the CPU " tip-bot for Morten Rasmussen
2018-07-20 13:32 ` [PATCH 4/4] arch/arm: Rebuild sched_domain hierarchy when cpu " Morten Rasmussen
2018-09-10 10:12   ` [tip:sched/core] sched/topology, arch/arm: Rebuild sched_domain hierarchy when CPU " tip-bot for Morten Rasmussen
2018-07-31 10:53 ` Peter Zijlstra [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=20180731105349.GQ2476@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=morten.rasmussen@arm.com \
    --cc=valentin.schneider@arm.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;
as well as URLs for NNTP newsgroup(s).