linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] sched/urgent for v6.5-rc2
Date: Sun, 16 Jul 2023 20:37:26 +0200	[thread overview]
Message-ID: <20230716183726.GEZLQ45tOt9L548BJ4@fat_crate.local> (raw)

Hi Linus,

please pull two urgent scheduler fixes for 6.5.

Thx.

---

The following changes since commit 06c2afb862f9da8dc5efa4b6076a0e48c3fbaaa5:

  Linux 6.5-rc1 (2023-07-09 13:53:13 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/sched_urgent_for_v6.5_rc2

for you to fetch changes up to aff037078ecaecf34a7c2afab1341815f90fba5e:

  sched/psi: use kernfs polling functions for PSI trigger polling (2023-07-10 09:52:30 +0200)

----------------------------------------------------------------
- Remove a cgroup from under a polling process properly

- Fix the idle sibling selection

----------------------------------------------------------------
Miaohe Lin (1):
      sched/fair: Use recent_used_cpu to test p->cpus_ptr

Suren Baghdasaryan (1):
      sched/psi: use kernfs polling functions for PSI trigger polling

 include/linux/psi.h       |  5 +++--
 include/linux/psi_types.h |  3 +++
 kernel/cgroup/cgroup.c    |  2 +-
 kernel/sched/fair.c       |  2 +-
 kernel/sched/psi.c        | 29 +++++++++++++++++++++--------
 5 files changed, 29 insertions(+), 12 deletions(-)

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2023-07-16 18:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-16 18:37 Borislav Petkov [this message]
2023-07-16 20:48 ` [GIT PULL] sched/urgent for v6.5-rc2 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=20230716183726.GEZLQ45tOt9L548BJ4@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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).