From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Frederic Barrat <fbarrat@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org
Cc: aneesh.kumar@linux.vnet.ibm.com, npiggin@gmail.com,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH 5/6] powerpc/mm: Optimize detection of thread local mm's
Date: Fri, 04 Aug 2017 22:58:36 +1000 [thread overview]
Message-ID: <1501851516.2664.89.camel@kernel.crashing.org> (raw)
In-Reply-To: <19e07887-2b70-324b-ae63-cb68a74f5fd8@linux.vnet.ibm.com>
On Fri, 2017-08-04 at 14:06 +0200, Frederic Barrat wrote:
> > +#ifdef CONFIG_PPC_BOOK3S_64
> > +static inline int mm_is_thread_local(struct mm_struct *mm)
> > +{
> > + if (atomic_read(&mm->context.active_cpus) > 1)
> > + return false;
> > + return cpumask_test_cpu(smp_processor_id(), mm_cpumask(mm));
> > +}
> > +#else /* CONFIG_PPC_BOOK3S_64 */
>
>
> While working on something related (mark memory context as needing
> global TLBI if used behind a NPU or PSL):
> http://patchwork.ozlabs.org/patch/796775/
>
> Michael raised the point that the store for the pte update cannot be
> reordered with the load which decides the scope of the TLBI, and had
> convinced me that a memory barrier was required.
>
> Couldn't we have the same problem here, where the atomic read is
> reordered with the store of the invalid PTE?
The store of the invalid PTE is done with a pte_update which contains a
sync as far as I can tell.
Cheers,
Ben.
next prev parent reply other threads:[~2017-08-04 12:59 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 4:27 [PATCH 1/6] powerpc/mm: Move pgdir setting into a helper Benjamin Herrenschmidt
2017-07-24 4:27 ` [PATCH 2/6] powerpc/mm: Avoid double irq save/restore in activate_mm Benjamin Herrenschmidt
2017-07-24 4:28 ` [PATCH 3/6] powerpc/mm: Ensure cpumask update is ordered Benjamin Herrenschmidt
2017-07-24 11:20 ` Nicholas Piggin
2017-07-24 20:54 ` Benjamin Herrenschmidt
2017-08-11 11:06 ` Nicholas Piggin
2017-08-11 22:40 ` Benjamin Herrenschmidt
2017-08-17 12:58 ` Michael Ellerman
2017-08-23 12:01 ` [3/6] " Michael Ellerman
2017-07-24 4:28 ` [PATCH 4/6] powerpc/mm: Use mm_is_thread_local() instread of open-coding Benjamin Herrenschmidt
2017-07-24 4:28 ` [PATCH 5/6] powerpc/mm: Optimize detection of thread local mm's Benjamin Herrenschmidt
2017-07-24 11:25 ` Nicholas Piggin
2017-07-24 13:46 ` Michael Ellerman
2017-07-25 0:34 ` Nicholas Piggin
2017-07-25 12:00 ` Michael Ellerman
2017-07-24 20:58 ` Benjamin Herrenschmidt
2017-07-25 0:44 ` Nicholas Piggin
2017-07-25 1:03 ` Benjamin Herrenschmidt
2017-07-25 10:55 ` Nicholas Piggin
2017-08-04 12:06 ` Frederic Barrat
2017-08-04 12:58 ` Benjamin Herrenschmidt [this message]
2017-08-21 17:27 ` Frederic Barrat
2017-08-21 17:35 ` Benjamin Herrenschmidt
2017-08-22 13:18 ` Frederic Barrat
2017-08-22 16:55 ` Benjamin Herrenschmidt
2017-08-24 16:40 ` Frederic Barrat
2017-08-24 18:47 ` Benjamin Herrenschmidt
2017-08-25 4:53 ` Frederic Barrat
2017-08-25 7:44 ` Benjamin Herrenschmidt
2017-08-25 8:03 ` Frederic Barrat
2017-08-22 4:28 ` Michael Ellerman
2017-07-24 4:28 ` [PATCH 6/6] powerpc/mm: Make switch_mm_irqs_off() out of line Benjamin Herrenschmidt
2017-08-24 12:37 ` [1/6] powerpc/mm: Move pgdir setting into a helper Michael Ellerman
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=1501851516.2664.89.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).