[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1521054910.11552.44.camel@synopsys.com>
Date: Wed, 14 Mar 2018 19:15:11 +0000
From: Alexey Brodkin <Alexey.Brodkin@...opsys.com>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
CC: "linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-snps-arc@...ts.infradead.org"
<linux-snps-arc@...ts.infradead.org>
Subject: Re: Do we need to disable preemption in flush_tlb_range()?
Ping!
On Thu, 2018-03-01 at 18:13 +0300, Alexey Brodkin wrote:
> Hi Vineet,
>
> Just noticed that in comments for smp_call_function_many() it is said that
> preemption must be disabled during its execution. And that function gets executed
> among other ways like that:
> -------------------------->8-----------------------
> flush_tlb_range()
> -> on_each_cpu_mask()
> -> smp_call_function_many()
> -------------------------->8-----------------------
>
> I'm not seeing right now any real problem with current implementation but
> some architectures do that thus the question.
>
> -Alexey
Powered by blists - more mailing lists