From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Ellerman <patch-notifications@ellerman.id.au>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
paulus@samba.org
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [v3,3/3] powerpc/mm/cxl: Add the fault handling cpu to mm cpumask
Date: Mon, 21 Aug 2017 09:49:15 -0700 [thread overview]
Message-ID: <1503334155.2195.17.camel@kernel.crashing.org> (raw)
In-Reply-To: <3xbZXv0yxCz9t0F@ozlabs.org>
On Mon, 2017-08-21 at 23:39 +1000, Michael Ellerman wrote:
> On Thu, 2017-07-27 at 06:24:55 UTC, "Aneesh Kumar K.V" wrote:
> > We use mm cpumask for serializing against lockless page table walk. Anybody
> > who is doing a lockless page table walk is expected to disable irq and only
> > cpus in mm cpumask is expected do the lockless walk. This ensure that
> > a THP split can send IPI to only cpus in the mm cpumask, to make sure there
> > are no parallel lockless page table walk.
> >
> > Add the CAPI fault handling cpu to the mm cpumask so that we can do the lockless
> > page table walk while inserting hash page table entries.
> >
> > Reviewed-by: Frederic Barrat <fbarrat@linux.vnet.ibm.com>
> > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
>
> Applied to powerpc next, thanks.
>
> https://git.kernel.org/powerpc/c/0f4bc0932e51817105fdee77a46680
Do you need barriers between the cpumask set and the walking ?
Cheers,
Ben.
next prev parent reply other threads:[~2017-08-21 18:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-27 6:24 [PATCH v3 1/3] powerpc/mm: Rename find_linux_pte_or_hugepte Aneesh Kumar K.V
2017-07-27 6:24 ` [PATCH v3 2/3] powerpc/mm: Don't send IPI to all cpus on THP updates Aneesh Kumar K.V
2017-08-21 13:39 ` [v3,2/3] " Michael Ellerman
2017-07-27 6:24 ` [PATCH v3 3/3] powerpc/mm/cxl: Add the fault handling cpu to mm cpumask Aneesh Kumar K.V
2017-08-21 13:39 ` [v3, " Michael Ellerman
2017-08-21 16:49 ` Benjamin Herrenschmidt [this message]
2017-08-21 13:39 ` [v3,1/3] powerpc/mm: Rename find_linux_pte_or_hugepte 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=1503334155.2195.17.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=patch-notifications@ellerman.id.au \
--cc=paulus@samba.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.