From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Subject: Re: Do we need to disable preemption in flush_tlb_range()?
Date: Wed, 14 Mar 2018 19:15:11 +0000 [thread overview]
Message-ID: <1521054910.11552.44.camel@synopsys.com> (raw)
In-Reply-To: <1519917189.13866.6.camel@synopsys.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: Do we need to disable preemption in flush_tlb_range()?
Date: Wed, 14 Mar 2018 19:15:11 +0000 [thread overview]
Message-ID: <1521054910.11552.44.camel@synopsys.com> (raw)
In-Reply-To: <1519917189.13866.6.camel@synopsys.com>
Ping!
On Thu, 2018-03-01@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
next prev parent reply other threads:[~2018-03-14 19:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 15:13 Do we need to disable preemption in flush_tlb_range()? Alexey Brodkin
2018-03-01 15:13 ` Alexey Brodkin
2018-03-14 19:15 ` Alexey Brodkin [this message]
2018-03-14 19:15 ` Alexey Brodkin
2018-03-14 20:19 ` Vineet Gupta
2018-03-14 20:19 ` Vineet Gupta
2018-03-15 8:27 ` Peter Zijlstra
2018-03-15 8:27 ` Peter Zijlstra
2018-03-15 8:27 ` Peter Zijlstra
2018-03-15 9:39 ` Alexey Brodkin
2018-03-15 9:39 ` Alexey Brodkin
2018-03-15 17:32 ` Vineet Gupta
2018-03-15 17:32 ` Vineet Gupta
2018-03-16 10:11 ` Peter Zijlstra
2018-03-16 10:11 ` Peter Zijlstra
2018-03-16 10:11 ` Peter Zijlstra
2018-03-16 15:01 ` Alexey Brodkin
2018-03-16 15:01 ` Alexey Brodkin
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=1521054910.11552.44.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
/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.