From: Rik van Riel <riel@surriel.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
akpm@linux-foundation.org,
Mel Gorman <mgorman@techsingularity.net>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/autonuma: don't use set_pte_at when updating protnone ptes
Date: Mon, 06 Feb 2017 13:46:22 -0500 [thread overview]
Message-ID: <1486406782.2096.9.camel@surriel.com> (raw)
In-Reply-To: <1486400776-28114-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Mon, 2017-02-06 at 22:36 +0530, Aneesh Kumar K.V wrote:
> Architectures like ppc64, use privilege access bit to mark pte non
> accessible.
> This implies that kernel can do a copy_to_user to an address marked
> for numa fault.
> This also implies that there can be a parallel hardware update for
> the pte.
> set_pte_at cannot be used in such scenarios. Hence switch the pte
> update to use ptep_get_and_clear and set_pte_at combination.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
Acked-by: Rik van Riel <riel@redhat.com>
--
All Rights Reversed.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2017-02-06 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 17:06 [PATCH] mm/autonuma: don't use set_pte_at when updating protnone ptes Aneesh Kumar K.V
2017-02-06 17:06 ` Aneesh Kumar K.V
2017-02-06 18:46 ` Rik van Riel [this message]
2017-02-06 22:26 ` Mel Gorman
2017-02-06 22:26 ` Mel Gorman
2017-02-07 8:09 ` John Hubbard
2017-02-14 14:11 ` Aneesh Kumar K.V
2017-02-14 14:11 ` Aneesh Kumar K.V
2017-02-15 0:05 ` Andrew Morton
2017-02-15 0:05 ` Andrew Morton
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=1486406782.2096.9.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
/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.