From: Peter Zijlstra <peterz@infradead.org>
To: Xuewen Yan <xuewen.yan@unisoc.com>
Cc: akpm@linux-foundation.org, oleg@redhat.com, longman@redhat.com,
dylanbhatch@google.com, rick.p.edgecombe@intel.com,
ke.wang@unisoc.com, xuewen.yan94@gmail.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] sched/proc: Print user_cpus_ptr for task status
Date: Mon, 29 Apr 2024 14:10:00 +0200 [thread overview]
Message-ID: <20240429121000.GA40213@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20240429084633.9800-1-xuewen.yan@unisoc.com>
On Mon, Apr 29, 2024 at 04:46:33PM +0800, Xuewen Yan wrote:
> The commit 851a723e45d1c("sched: Always clear user_cpus_ptr in do_set_cpus_allowed()")
> would clear the user_cpus_ptr when call the do_set_cpus_allowed.
>
> In order to determine whether the user_cpus_ptr is taking effect,
> it is better to print the task's user_cpus_ptr.
This is an ABI change and would mandate we forever more have this
distinction. I don't think your changes justifies things sufficiently
for this.
next prev parent reply other threads:[~2024-04-29 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-29 8:46 [PATCH] sched/proc: Print user_cpus_ptr for task status Xuewen Yan
2024-04-29 12:10 ` Peter Zijlstra [this message]
2024-05-06 8:04 ` Xuewen Yan
2024-05-06 18:03 ` Waiman Long
2024-05-07 6:57 ` Xuewen Yan
2024-05-08 17:01 ` 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=20240429121000.GA40213@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dylanbhatch@google.com \
--cc=ke.wang@unisoc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=oleg@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=xuewen.yan94@gmail.com \
--cc=xuewen.yan@unisoc.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