public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Valentin Schneider <vschneid@redhat.com>,
	Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: [GIT PULL] Scheduler changes for v6.9
Date: Mon, 11 Mar 2024 13:17:48 +0100	[thread overview]
Message-ID: <Ze72bF17UQpj7ZZy@gmail.com> (raw)

Linus,

Please pull the latest sched/core git tree from:

   git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-core-2024-03-11

   # HEAD: 54de442747037485da1fc4eca9636287a61e97e3 sched/topology: Rename SD_SHARE_PKG_RESOURCES to SD_SHARE_LLC

Scheduler changes for v6.9:

 - Fix inconsistency in misfit task load-balancing

 - Fix CPU isolation bugs in the task-wakeup logic

 - Rework & unify the sched_use_asym_prio() and sched_asym_prefer() logic

 - Clean up & simplify ->avg_* accesses

 - Misc cleanups & fixes

 Thanks,

	Ingo

------------------>
Alex Shi (5):
      sched/topology: Remove duplicate descriptions from TOPOLOGY_SD_FLAGS
      sched/fair: Remove unused parameter from sched_asym()
      sched/fair: Rework sched_use_asym_prio() and sched_asym_prefer()
      sched/fair: Check the SD_ASYM_PACKING flag in sched_use_asym_prio()
      sched/topology: Rename SD_SHARE_PKG_RESOURCES to SD_SHARE_LLC

David Vernet (3):
      sched/fair: Remove unnecessary goto in update_sd_lb_stats()
      sched/fair: Do strict inequality check for busiest misfit task group
      sched/fair: Simplify the update_sd_pick_busiest() logic

Keisuke Nishimura (2):
      sched/fair: Take the scheduling domain into account in select_idle_smt()
      sched/fair: Take the scheduling domain into account in select_idle_core()

Shrikanth Hegde (3):
      sched/core: Simplify code by removing duplicate #ifdefs
      sched/fair: Use existing helper functions to access ->avg_rt and ->avg_dl
      sched/fair: Add READ_ONCE() and use existing helper function to access ->avg_irq


 arch/powerpc/kernel/smp.c      |   6 +--
 include/linux/sched/sd_flags.h |   4 +-
 include/linux/sched/topology.h |   6 +--
 kernel/sched/core.c            |   4 +-
 kernel/sched/fair.c            | 110 +++++++++++++++++------------------------
 kernel/sched/sched.h           |   2 +-
 kernel/sched/topology.c        |  35 ++++++-------
 7 files changed, 74 insertions(+), 93 deletions(-)

             reply	other threads:[~2024-03-11 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 12:17 Ingo Molnar [this message]
2024-03-12  3:32 ` [GIT PULL] Scheduler changes for v6.9 pr-tracker-bot

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=Ze72bF17UQpj7ZZy@gmail.com \
    --to=mingo@kernel.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=sshegde@linux.ibm.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.com \
    /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