[GIT PULL] scheduler updates for v4.20

[GIT PULL] scheduler updates for v4.20

[Ingo Molnar]

Linus,

Please pull the latest sched-core-for-linus git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-for-linus

   # HEAD: 11e13696a08e838ba48c72404c2b3f41429b5b20 sched/completions/Documentation: Add recommendation for dynamic and ONSTACK completions

The main changes are:

 - Migrate CPU-intense 'misfit' tasks on asymmetric capacity systems, to 
   better utilize (much) faster 'big core' CPUs.
   (Morten Rasmussen, Valentin Schneider)

 - Topology handling improvements, in particular when CPU capacity 
   changes and related load-balancing fixes/improvements (Morten Rasmussen)

 - ... plus misc other improvements, fixes and updates.

 Thanks,

	Ingo

------------------>
Borislav Petkov (1):
      cpu/SMT: State SMT is disabled even with nosmt and without "=force"

Chris Redpath (1):
      sched/fair: Don't move tasks to lower capacity CPUs unless necessary

Dietmar Eggemann (2):
      sched/fair: Disable LB_BIAS by default
      sched/fair: Remove setting task's se->runnable_weight during PELT update

Ingo Molnar (1):
      sched/completions/Documentation: Clean up the document some more

John Garry (1):
      sched/completions/Documentation: Fix a couple of punctuation nits

Morten Rasmussen (9):
      sched/topology: Add SD_ASYM_CPUCAPACITY flag detection
      sched/topology, drivers/base/arch_topology: Rebuild the sched_domain hierarchy when capacities change
      sched/topology, arch/arm64: Rebuild the sched_domain hierarchy when the CPU capacity changes
      sched/topology, arch/arm: Rebuild sched_domain hierarchy when CPU capacity changes
      sched/topology: Add static_key for asymmetric CPU capacity optimizations
      sched/fair: Add 'group_misfit_task' load-balance type
      sched/fair: Add sched_group per-CPU max capacity
      sched/fair: Consider misfit tasks when load-balancing
      sched/core: Disable SD_PREFER_SIBLING on asymmetric CPU capacity domains

Nicholas Mc Guire (1):
      sched/completions/Documentation: Add recommendation for dynamic and ONSTACK completions

Peter Zijlstra (1):
      sched/debug: Explicitly cast sched_feat() to bool

Rafael J. Wysocki (1):
      sched/core: Fix comment regarding nr_iowait_cpu() and get_iowait_load()

Uwe Kleine-König (1):
      sched/debug: Use symbolic names for task state constants

Valentin Schneider (5):
      sched/fair: Kick nohz balance if rq->misfit_task_load
      sched/fair: Change 'prefer_sibling' type to bool
      sched/core: Change root_domain->overload type to int
      sched/fair: Wrap rq->rd->overload accesses with READ/WRITE_ONCE()
      sched/fair: Set rq->rd->overload when misfit

Vincent Guittot (3):
      sched/numa: Remove unused code from update_numa_stats()
      sched/numa: Remove unused numa_stats::nr_running field
      sched/pelt: Fix warning and clean up IRQ PELT config

zhong jiang (1):
      sched/topology: Make local variables static

Re: [GIT PULL] scheduler updates for v4.20

[Linus Torvalds]

On Tue, Oct 23, 2018 at 12:06 PM Ingo Molnar <mingo@kernel.org> wrote:
>
> Please pull the latest sched-core-for-linus git tree from:

Hmm. I've pulled, but this message was odd and mis-formed.

First off, it didn't have a diffstat (I did verify the shortlog instead).

Secondly, can you please check how you send emails. I get a DMARC
failure on that email, looking like this:

  ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@gmail.com header.s=20161025 header.b=iFVXLHcJ;
       spf=pass (google.com: domain of mingo.kernel.org@gmail.com
designates 209.85.220.65 as permitted sender)
smtp.mailfrom=mingo.kernel.org@gmail.com;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org

so it seems something is unhappy with how you had that

   Sender: Ingo Molnar <mingo.kernel.org@gmail.com>
   From: Ingo Molnar <mingo@kernel.org>

set up. It looks like you went directly through gmail rather than
going through kernel.org and getting a proper kernel.org dkim hash.

Thirdly (and least importantly), you should probably check your MUA
(which seems to be Mutt), because this came in with

  Content-Type: text/plain; charset=iso-8859-1
  Content-Disposition: inline
  Content-Transfer-Encoding: 8bit

and using iso-8859-1 instead of utf-8 in this day and age is just all
kinds of odd.  It looks like it was all fine, but if Mutt has an
option to just send as utf-8, I encourae everybody to just use that
and try to just have utf-8 everywhere. We've had too many silly issues
when people mix locales etc and some point in the chain gets it
wrong..

                Linus