From: Tejun Heo <tj@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Lai Jiangshan <jiangshanlai@gmail.com>
Subject: [GIT PULL] workqueue changes for v4.18-rc1
Date: Tue, 5 Jun 2018 12:26:14 -0700 [thread overview]
Message-ID: <20180605192614.GH1351649@devbig577.frc2.facebook.com> (raw)
Hello, Linus.
* Patches to make kworkers to report the workqueue it is executing or
has executed most recently in /proc/PID/comm.
* CONFIG_SMP shuffle to move stuff which isn't necessary for UP builds
inside CONFIG_SMP.
Thanks.
The following changes since commit e6506eb241871d68647c53cb6d0a16299550ae97:
Merge tag 'trace-v4.17-rc4-2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace (2018-05-16 16:45:23 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git for-4.18
for you to fetch changes up to 66448bc274cadedb71fda7d914e7c29d8dead217:
workqueue: move function definitions within CONFIG_SMP block (2018-05-23 11:16:58 -0700)
----------------------------------------------------------------
Mathieu Malaterre (1):
workqueue: move function definitions within CONFIG_SMP block
Tejun Heo (6):
workqueue: Replace pool->attach_mutex with global wq_pool_attach_mutex
workqueue: Make worker_attach/detach_pool() update worker->pool
workqueue: Set worker->desc to workqueue name by default
proc: Consolidate task->comm formatting into proc_task_name()
workqueue: Show the latest workqueue name in /proc/PID/{comm,stat,status}
workqueue: Make sure struct worker is accessible for wq_worker_comm()
fs/proc/array.c | 33 ++++++-----
fs/proc/base.c | 5 +-
fs/proc/internal.h | 2 +
include/linux/workqueue.h | 1 +
kernel/workqueue.c | 139 +++++++++++++++++++++++++++++---------------
kernel/workqueue_internal.h | 3 +-
6 files changed, 119 insertions(+), 64 deletions(-)
--
tejun
reply other threads:[~2018-06-05 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180605192614.GH1351649@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=jiangshanlai@gmail.com \
--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