mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Chuyi Zhou <zhouchuyi@bytedance.com>,
	tglx@kernel.org, mingo@redhat.com, luto@kernel.org,
	peterz@infradead.org, paulmck@kernel.org, muchun.song@linux.dev,
	bp@alien8.de, dave.hansen@linux.intel.com, pbonzini@redhat.com,
	bigeasy@linutronix.de, clrkwllms@kernel.org, rostedt@goodmis.org,
	nadav.amit@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 11/12] x86/mm: Enable preemption during native_flush_tlb_multi
Date: Thu, 4 Jun 2026 14:15:07 -0700	[thread overview]
Message-ID: <60106147-5f4c-44c1-b972-e51099917bdb@intel.com> (raw)
In-Reply-To: <20260528151338.617843-12-zhouchuyi@bytedance.com>

First, the subject needs some improvement. Add parenthesis to
functions(), please. Second, it's literally wrong: "Enable preemption
during native_flush_tlb_multi". It does not do that or it at least
describes it badly.

It enables preemption during *one* call to native_flush_tlb_multi().

> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
> index 29226d112029..d540f54f4d16 100644
> --- a/arch/x86/kernel/kvm.c
> +++ b/arch/x86/kernel/kvm.c
> @@ -662,8 +662,10 @@ static void kvm_flush_tlb_multi(const struct cpumask *cpumask,
>  	u8 state;
>  	int cpu;
>  	struct kvm_steal_time *src;
> -	struct cpumask *flushmask = this_cpu_cpumask_var_ptr(__pv_cpu_mask);
> +	struct cpumask *flushmask;
>  
> +	guard(preempt)();
> +	flushmask = this_cpu_cpumask_var_ptr(__pv_cpu_mask);
>  	cpumask_copy(flushmask, cpumask);
>  	/*
>  	 * We have to call flush only on online vCPUs. And

This KVM modification is a complete non sequitur. It comes from nowhere.
No comments. No mention in the changelog.

Now, looking at how it's called, I guess flush_tlb_multi() lands here
because of pv_ops. But, please have mercy on the poor reviewers and walk
them through this.

This could also be done in a separate patch. It's OK to disable
preemption twice.

> diff --git a/arch/x86/mm/tlb.c b/arch/x86/mm/tlb.c
> index cfc3a72477f5..58c6f3d2f993 100644
> --- a/arch/x86/mm/tlb.c
> +++ b/arch/x86/mm/tlb.c
> @@ -1421,9 +1421,11 @@ void flush_tlb_mm_range(struct mm_struct *mm, unsigned long start,
>  	if (mm_global_asid(mm)) {
>  		broadcast_tlb_flush(info);
>  	} else if (cpumask_any_but(mm_cpumask(mm), cpu) < nr_cpu_ids) {
> +		put_cpu();
>  		info->trim_cpumask = should_trim_cpumask(mm);
>		flush_tlb_multi(mm_cpumask(mm), info);
>  		consider_global_asid(mm);
> +		goto invalidate;
>  	} else if (mm == this_cpu_read(cpu_tlbstate.loaded_mm)) {
>  		lockdep_assert_irqs_enabled();
>  		local_irq_disable();
> @@ -1432,6 +1434,7 @@ void flush_tlb_mm_range(struct mm_struct *mm, unsigned long start,
>  	}
>  
>  	put_cpu();
> +invalidate:
>  	mmu_notifier_arch_invalidate_secondary_tlbs(mm, start, end);
>  }

I really don't like the goto. Can this be refactored to not use a goto?

I'd honestly rather it be:

	if (foo) {
		broadcast_tlb_flush(info);
		put_cpu();
	} else if (bar) {
		put_cpu();
		flush_tlb_multi();
	} else {
		flush_tlb_func(info);
		put_cpu();
	}

than have the goto. At least that ^ makes it obvious that each case
needs a put_cpu(). But I also just generally don't like how the code is
structured at this point.

Does anybody have any smart ideas?

> @@ -1691,7 +1694,9 @@ void arch_tlbbatch_flush(struct arch_tlbflush_unmap_batch *batch)
>  		invlpgb_flush_all_nonglobals();
>  		batch->unmapped_pages = false;
>  	} else if (cpumask_any_but(&batch->cpumask, cpu) < nr_cpu_ids) {
> +		put_cpu();
>  		flush_tlb_multi(&batch->cpumask, &info);
> +		goto clear;
>  	} else if (cpumask_test_cpu(cpu, &batch->cpumask)) {
>  		lockdep_assert_irqs_enabled();
>  		local_irq_disable();
> @@ -1699,9 +1704,9 @@ void arch_tlbbatch_flush(struct arch_tlbflush_unmap_batch *batch)
>  		local_irq_enable();
>  	}
>  
> -	cpumask_clear(&batch->cpumask);
> -
>  	put_cpu();
> +clear:
> +	cpumask_clear(&batch->cpumask);
>  }

I have the same general complaint about this one. This is really just
hacked into place, leaving a mess for everyone in the future. It needs
some careful refactoring.

  reply	other threads:[~2026-06-04 21:15 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 15:13 [PATCH v6 00/12] Allow preemption during IPI completion waiting to improve real-time performance Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 01/12] smp: Disable preemption explicitly in __csd_lock_wait Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 02/12] smp: Enable preemption early in smp_call_function_single Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 03/12] smp: Refactor remote CPU selection in smp_call_function_any() Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 04/12] smp: Use task-local IPI cpumask in smp_call_function_many_cond() Chuyi Zhou
2026-06-03 10:54   ` Sebastian Andrzej Siewior
2026-06-03 11:48     ` Chuyi Zhou
2026-06-03 12:21       ` Sebastian Andrzej Siewior
2026-05-28 15:13 ` [PATCH v6 05/12] smp: Alloc percpu csd data in smpcfd_prepare_cpu() only once Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 06/12] smp: Enable preemption early in smp_call_function_many_cond Chuyi Zhou
2026-06-03 11:00   ` Sebastian Andrzej Siewior
2026-06-03 11:54     ` Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 07/12] smp: Remove preempt_disable from smp_call_function Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 08/12] smp: Remove preempt_disable from on_each_cpu_cond_mask Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 09/12] scftorture: Remove preempt_disable in scftorture_invoke_one Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 10/12] x86/mm: Move flush_tlb_info back to the stack Chuyi Zhou
2026-06-04 20:54   ` Dave Hansen
2026-06-04 21:11     ` Nadav Amit
2026-06-04 21:16       ` Dave Hansen
2026-06-04 21:21         ` Nadav Amit
2026-06-05  2:54           ` Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 11/12] x86/mm: Enable preemption during native_flush_tlb_multi Chuyi Zhou
2026-06-04 21:15   ` Dave Hansen [this message]
2026-06-05  3:36     ` Chuyi Zhou
2026-05-28 15:13 ` [PATCH v6 12/12] x86/mm: Enable preemption during flush_tlb_kernel_range Chuyi Zhou
2026-06-04 21:21   ` Dave Hansen
2026-06-05  3:51     ` Chuyi Zhou
2026-05-28 19:47 ` [PATCH v6 00/12] Allow preemption during IPI completion waiting to improve real-time performance Paul E. McKenney
2026-05-29  3:22   ` Chuyi Zhou
2026-05-29  6:41     ` Sebastian Andrzej Siewior
2026-06-03 11:02 ` Sebastian Andrzej Siewior

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=60106147-5f4c-44c1-b972-e51099917bdb@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bigeasy@linutronix.de \
    --cc=bp@alien8.de \
    --cc=clrkwllms@kernel.org \
    --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=nadav.amit@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@kernel.org \
    --cc=zhouchuyi@bytedance.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

all inboxes | Powered by JetHome®