linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] workqueue changes for-6.5
Date: Mon, 26 Jun 2023 11:45:28 -1000	[thread overview]
Message-ID: <ZJoG-BptcGoHII35@slm.duckdns.org> (raw)

The following changes since commit ba0ad6ed89fd5dada3b7b65ef2b08e95d449d4ab:

  media: nxp: imx8-isi: fix buiding on 32-bit (2023-05-08 09:10:07 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git/ tags/wq-for-6.5

for you to fetch changes up to 18c8ae813156a6855f026de80fffb91e1a28ab3d:

  workqueue: Disable per-cpu CPU hog detection when wq_cpu_intensive_thresh_us is 0 (2023-05-25 10:46:53 -1000)

----------------------------------------------------------------
workqueue: Changes for v6.5

* Concurrency-managed per-cpu work items that hog CPUs and delay the
  execution of other work items are now automatically detected and excluded
  from concurrency management. Reporting on such work items can also be
  enabled through a config option.

* Added tools/workqueue/wq_monitor.py which improves visibility into
  workqueue usages and behaviors.

* Includes Arnd's minimal fix for gcc-13 enum warning on 32bit compiles.
  This conflicts with afa4bb778e48 ("workqueue: clean up WORK_* constant
  types, clarify masking") in master. Can be resolved by picking the master
  version.

----------------------------------------------------------------
Arnd Bergmann (1):
      workqueue: fix enum type for gcc-13

Paul E. McKenney (1):
      Further upgrade queue_work_on() comment

Tejun Heo (7):
      workqueue: Add pwq->stats[] and a monitoring script
      workqueue: Re-order struct worker fields
      workqueue: Move worker_set/clr_flags() upwards
      workqueue: Improve locking rule description for worker fields
      workqueue: Automatically mark CPU-hogging work items CPU_INTENSIVE
      workqueue: Report work funcs that trigger automatic CPU_INTENSIVE mechanism
      workqueue: Track and monitor per-workqueue CPU time usage

Zqiang (2):
      workqueue: Fix WARN_ON_ONCE() triggers in worker_enter_idle()
      workqueue: Disable per-cpu CPU hog detection when wq_cpu_intensive_thresh_us is 0

 Documentation/admin-guide/kernel-parameters.txt |  12 +
 Documentation/core-api/workqueue.rst            |  32 +++
 include/linux/workqueue.h                       |   2 +-
 kernel/sched/core.c                             |   3 +
 kernel/workqueue.c                              | 322 +++++++++++++++++++-----
 kernel/workqueue_internal.h                     |  24 +-
 lib/Kconfig.debug                               |  13 +
 tools/workqueue/wq_monitor.py                   | 168 +++++++++++++
 8 files changed, 500 insertions(+), 76 deletions(-)
 create mode 100644 tools/workqueue/wq_monitor.py

             reply	other threads:[~2023-06-26 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 21:45 Tejun Heo [this message]
2023-06-28  0:05 ` [GIT PULL] workqueue changes for-6.5 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=ZJoG-BptcGoHII35@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).