From: Waiman Long <longman@redhat.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
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>,
Valentin Schneider <vschneid@redhat.com>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-doc@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Nico Pache <npache@redhat.com>, Phil Auld <pauld@redhat.com>,
John Coleman <jocolema@redhat.com>,
Waiman Long <longman@redhat.com>
Subject: [PATCH v2 0/2] sched/core: Show user_cpus_ptr & allow its reset
Date: Wed, 29 Oct 2025 17:55:53 -0400 [thread overview]
Message-ID: <20251029215555.1006595-1-longman@redhat.com> (raw)
v2: Make minor change in patch 2 to show the new status fields will be
empty if user_cpus_ptr not defined.
As the presence of user_cpus_ptr will affect how the CPU affinity of a
process will be defined, it makes sense to enable users to see if the
user_cpus_ptr of a process is set as well as enabling the clearing of
user_cpus_ptr if it is not needed.
Waiman Long (2):
sched/core: Enable full cpumask to clear user cpumask in
sched_setaffinity()
fs/proc: Show the content of task->user_cpus_ptr in /proc/<pid>/status
Documentation/filesystems/proc.rst | 3 +++
fs/proc/array.c | 9 +++++++++
kernel/sched/syscalls.c | 20 ++++++++++++++------
3 files changed, 26 insertions(+), 6 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-29 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 21:55 Waiman Long [this message]
2025-10-29 21:55 ` [PATCH v2 1/2] sched/core: Enable full cpumask to clear user cpumask in sched_setaffinity() Waiman Long
2025-10-29 21:55 ` [PATCH v2 2/2] fs/proc: Show the content of task->user_cpus_ptr in /proc/<pid>/status Waiman Long
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=20251029215555.1006595-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dietmar.eggemann@arm.com \
--cc=jocolema@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=npache@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).