From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Chen, Yu C" <yu.c.chen@intel.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Ingo Molnar <mingo@kernel.org>,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Juri Lelli <juri.lelli@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Valentin Schneider <vschneid@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
aubrey.li@linux.intel.com
Subject: Re: [tip:sched/core] [sched/smp] 06ddd17521: BUG:using_smp_processor_id()in_preemptible
Date: Thu, 10 Jul 2025 10:11:14 +0200 [thread overview]
Message-ID: <20250710081114.5wnABNG7@linutronix.de> (raw)
In-Reply-To: <292e70ed-aae5-4f52-8f85-80cba7ff301d@intel.com>
On 2025-07-10 16:00:46 [+0800], Chen, Yu C wrote:
> migrate_disable() disables the task migration between CPUs by restricting
> the task's affinity, but it does not disable the preemption on single
> CPUs IMO. The scope of guard(preempt)() in migrate_disable() is just
> within the migrate_disable(). debug_smp_processor_id() warns when the
> preemption is enabled.
does migrate_disable() really have no effect on
debug_smp_processor_id()?
> Thanks,
> Chenyu
Sebastian
next prev parent reply other threads:[~2025-07-10 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 2:58 [tip:sched/core] [sched/smp] 06ddd17521: BUG:using_smp_processor_id()in_preemptible kernel test robot
2025-07-10 3:18 ` Chen, Yu C
2025-07-10 6:25 ` Sebastian Andrzej Siewior
2025-07-10 8:00 ` Chen, Yu C
2025-07-10 8:11 ` Sebastian Andrzej Siewior [this message]
2025-07-10 8:27 ` [PATCH] lib/smp_processor_id: Make migration check unconditional of SMP Sebastian Andrzej Siewior
2025-07-10 8:32 ` Chen, Yu C
2025-07-10 10:13 ` Peter Zijlstra
2025-07-11 12:41 ` [tip: sched/core] " tip-bot2 for Sebastian Andrzej Siewior
2025-07-10 8:29 ` [tip:sched/core] [sched/smp] 06ddd17521: BUG:using_smp_processor_id()in_preemptible Chen, Yu C
2025-07-10 10:47 ` Sebastian Andrzej Siewior
2025-07-10 11:31 ` Chen, Yu C
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=20250710081114.5wnABNG7@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=aubrey.li@linux.intel.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sshegde@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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).