[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <40f86e4b-8426-1a71-2ab5-4c5523dba247@rasmusvillemoes.dk>
Date: Mon, 22 Jul 2019 21:47:00 +0200
From: Rasmus Villemoes <linux@...musvillemoes.dk>
To: Nadav Amit <namit@...are.com>, Andy Lutomirski <luto@...nel.org>,
Dave Hansen <dave.hansen@...ux.intel.com>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
Rik van Riel <riel@...riel.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Joe Perches <joe@...ches.com>
Subject: Re: [PATCH v3 3/9] x86/mm/tlb: Open-code on_each_cpu_cond_mask() for
tlb_is_not_lazy()
On 19/07/2019 02.58, Nadav Amit wrote:
> /*
> @@ -865,7 +893,7 @@ void arch_tlbbatch_flush(struct arch_tlbflush_unmap_batch *batch)
> if (cpumask_test_cpu(cpu, &batch->cpumask)) {
> lockdep_assert_irqs_enabled();
> local_irq_disable();
> - flush_tlb_func_local(&full_flush_tlb_info);
> + flush_tlb_func_local((void *)&full_flush_tlb_info);
> local_irq_enable();
> }
I think the confusion could be cleared up if you moved this hunk to
patch 2 where it belongs - i.e. where you change the prototype of
flush_tlb_func_local() and hence introduce the warning.
Rasmus
Powered by blists - more mailing lists