mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chuyi Zhou" <zhouchuyi@bytedance.com>
To: "Peter Zijlstra" <peterz@infradead.org>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <luto@kernel.org>,
	 <paulmck@kernel.org>, <muchun.song@linux.dev>, <bp@alien8.de>,
	 <dave.hansen@linux.intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/11] smp: Use on-stack cpumask in smp_call_function_many_cond
Date: Fri, 6 Feb 2026 17:07:05 +0800	[thread overview]
Message-ID: <f2adb710-dd8a-4b41-8511-0466e68d3635@bytedance.com> (raw)
In-Reply-To: <20260205094422.GG232055@noisy.programming.kicks-ass.net>

在 2026/2/5 17:44, Peter Zijlstra 写道:
> On Tue, Feb 03, 2026 at 07:23:54PM +0800, Chuyi Zhou wrote:
>> This patch use on-stack cpumask to replace percpu cfd cpumask in
>> smp_call_function_many_cond(). alloc_cpumask_var() may fail when
>> CONFIG_CPUMASK_OFFSTACK is enabled. In such extreme case, fall back to
>> cfd->cpumask. This is a preparation for the next patch.
>>
>> Signed-off-by: Chuyi Zhou <zhouchuyi@bytedance.com>
>> ---
>>   kernel/smp.c | 22 +++++++++++++++++-----
>>   1 file changed, 17 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/smp.c b/kernel/smp.c
>> index f572716c3c7d..35948afced2e 100644
>> --- a/kernel/smp.c
>> +++ b/kernel/smp.c
>> @@ -805,11 +805,17 @@ static void smp_call_function_many_cond(const struct cpumask *mask,
>>   	int cpu, last_cpu, this_cpu = smp_processor_id();
>>   	struct call_function_data *cfd;
>>   	bool wait = scf_flags & SCF_WAIT;
>> +	bool preemptible_wait = true;
>> +	cpumask_var_t cpumask_stack;
>> +	struct cpumask *cpumask;
>>   	int nr_cpus = 0;
>>   	bool run_remote = false;
>>   
>>   	lockdep_assert_preemption_disabled();
>>   
>> +	if (!alloc_cpumask_var(&cpumask_stack, GFP_ATOMIC))
>> +		preemptible_wait = false;
> 
> IIRC this breaks RT, must not allocate with preemption disabled.

Thank you for the reminder.

Perhaps another feasible approach is only consider 
CONFIG_CPUMASK_OFFSTACK=n.

Of course, if we use cpus_read_lock and ensure that the caller’s context 
is sleepable, this issue would also be eliminated.

  reply	other threads:[~2026-02-06  9:07 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 11:23 [PATCH 00/11] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-02-03 11:23 ` [PATCH 01/11] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-02-05  6:05   ` Muchun Song
2026-02-03 11:23 ` [PATCH 02/11] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-02-05  3:55   ` Muchun Song
2026-02-05  9:34   ` Peter Zijlstra
2026-02-03 11:23 ` [PATCH 03/11] smp: Remove get_cpu from smp_call_function_any Chuyi Zhou
2026-02-05  6:03   ` Muchun Song
2026-02-05  9:42   ` Peter Zijlstra
2026-02-06  8:54     ` Chuyi Zhou
2026-02-03 11:23 ` [PATCH 04/11] smp: Use on-stack cpumask in smp_call_function_many_cond Chuyi Zhou
2026-02-05  9:44   ` Peter Zijlstra
2026-02-06  9:07     ` Chuyi Zhou [this message]
2026-02-05  9:51   ` Peter Zijlstra
2026-02-03 11:23 ` [PATCH 05/11] smp: Enable preemption early " Chuyi Zhou
2026-02-05  9:52   ` Peter Zijlstra
2026-02-05 10:57     ` Peter Zijlstra
2026-02-05 14:29       ` Chuyi Zhou
2026-02-05 14:59         ` Peter Zijlstra
2026-02-06  8:43           ` Chuyi Zhou
2026-02-06  9:47             ` Peter Zijlstra
2026-02-06 11:45               ` Chuyi Zhou
2026-02-09  7:56     ` Chuyi Zhou
2026-02-03 11:23 ` [PATCH 06/11] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-02-03 11:23 ` [PATCH 07/11] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-02-03 11:23 ` [PATCH 08/11] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-02-03 11:23 ` [PATCH 09/11] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-02-03 11:24 ` [PATCH 10/11] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-02-03 11:24 ` [PATCH 11/11] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou

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=f2adb710-dd8a-4b41-8511-0466e68d3635@bytedance.com \
    --to=zhouchuyi@bytedance.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=muchun.song@linux.dev \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®