All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nadav Amit <namit@vmware.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>, Andy Lutomirski <luto@kernel.org>,
	Borislav Petkov <bp@alien8.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Rik van Riel <riel@surriel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [RFC PATCH 3/6] smp: Run functions concurrently in smp_call_function_many()
Date: Mon, 27 May 2019 17:39:35 +0000	[thread overview]
Message-ID: <57E94109-CBE8-43BA-98FF-646E8C9EE8A2@vmware.com> (raw)
In-Reply-To: <20190527091534.GS2623@hirez.programming.kicks-ass.net>

> On May 27, 2019, at 2:15 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> 
>> +		/*
>> +		 * Choose the most efficient way to send an IPI. Note that the
>> +		 * number of CPUs might be zero due to concurrent changes to the
>> +		 * provided mask or cpu_online_mask.
>> +		 */
> 
> Since we have preemption disabled here, I don't think online mask can
> shrink, cpu-offline uses stop_machine().

Right. So I’ll update the comment, but IIUC the provided mask might still
change, so I’ll leave the rest of the comment and the code as is.

>> +		if (nr_cpus == 1)
>> +			arch_send_call_function_single_ipi(last_cpu);
>> +		else if (likely(nr_cpus > 1))
>> +			arch_send_call_function_ipi_mask(cfd->cpumask_ipi);
>> +	}



  reply	other threads:[~2019-05-27 17:39 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-25  8:21 [RFC PATCH 0/6] x86/mm: Flush remote and local TLBs concurrently Nadav Amit
2019-05-25  8:21 ` [RFC PATCH 1/6] smp: Remove smp_call_function() and on_each_cpu() return values Nadav Amit
2019-05-25  8:21 ` [RFC PATCH 2/6] cpumask: Purify cpumask_next() Nadav Amit
2019-05-25  8:32   ` Ingo Molnar
2019-05-27  8:30   ` Peter Zijlstra
2019-05-27 17:34     ` Nadav Amit
2019-05-25  8:22 ` [RFC PATCH 3/6] smp: Run functions concurrently in smp_call_function_many() Nadav Amit
2019-05-27  9:15   ` Peter Zijlstra
2019-05-27 17:39     ` Nadav Amit [this message]
2019-05-25  8:22 ` [RFC PATCH 4/6] x86/mm/tlb: Refactor common code into flush_tlb_on_cpus() Nadav Amit
2019-05-27  9:24   ` Peter Zijlstra
2019-05-27 18:59     ` Nadav Amit
2019-05-27 19:14       ` Peter Zijlstra
2019-05-25  8:22 ` [RFC PATCH 5/6] x86/mm/tlb: Flush remote and local TLBs concurrently Nadav Amit
2019-05-25  8:22   ` [Xen-devel] " Nadav Amit
2019-05-25  8:22   ` Nadav Amit via Virtualization
2019-05-25  8:38   ` Nadav Amit
2019-05-25  8:38   ` Nadav Amit
2019-05-25  8:38     ` [Xen-devel] " Nadav Amit
2019-05-25  8:38     ` Nadav Amit via Virtualization
2019-05-25  8:54   ` Juergen Gross
2019-05-25  8:54     ` [Xen-devel] " Juergen Gross
2019-05-27  9:47     ` Peter Zijlstra
2019-05-27  9:47     ` Peter Zijlstra
2019-05-27  9:47       ` [Xen-devel] " Peter Zijlstra
2019-05-27 10:21       ` Paolo Bonzini
2019-05-27 10:21       ` Paolo Bonzini
2019-05-27 10:21         ` [Xen-devel] " Paolo Bonzini
2019-05-27 12:32         ` Peter Zijlstra
2019-05-27 12:32         ` Peter Zijlstra
2019-05-27 12:32           ` [Xen-devel] " Peter Zijlstra
2019-05-27 12:32           ` Peter Zijlstra
2019-05-27 12:45           ` Paolo Bonzini
2019-05-27 12:45           ` Paolo Bonzini
2019-05-27 12:45             ` [Xen-devel] " Paolo Bonzini
2019-05-27 12:45           ` Paolo Bonzini
2019-05-27 10:21       ` Paolo Bonzini
2019-05-27 17:49       ` Nadav Amit
2019-05-27 17:49         ` [Xen-devel] " Nadav Amit
2019-05-27 17:49       ` Nadav Amit
2019-05-27 17:49       ` Nadav Amit via Virtualization
2019-05-27  9:47     ` Peter Zijlstra
2019-05-25  8:54   ` Juergen Gross
2019-05-25  8:54   ` Juergen Gross
2019-05-25  8:22 ` Nadav Amit
2019-05-25  8:22 ` [RFC PATCH 6/6] x86/mm/tlb: Optimize local TLB flushes Nadav Amit
2019-05-27  8:28 ` [RFC PATCH 0/6] x86/mm: Flush remote and local TLBs concurrently Peter Zijlstra
2019-05-27  9:59 ` Peter Zijlstra

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=57E94109-CBE8-43BA-98FF-646E8C9EE8A2@vmware.com \
    --to=namit@vmware.com \
    --cc=bp@alien8.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.