Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1575210

Re: [PATCH] mm/autonuma: don't use set_pte_at when updating protnone ptes

Show all headers | View raw

On Mon, Feb 06, 2017 at 10:36:16PM +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>

Yeah, ok. The main thing is that it still avoids doing an unnecessary TLB
flush so

Acked-by: Mel Gorman <mgorman@techsingularity.net>

-- 
Mel Gorman
SUSE Labs

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH] mm/autonuma: don't use set_pte_at when updating protnone ptes "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com> - 2017-02-06 18:10 +0100
  Re: [PATCH] mm/autonuma: don't use set_pte_at when updating  protnone ptes Rik van Riel <riel@surriel.com> - 2017-02-06 19:50 +0100
  Re: [PATCH] mm/autonuma: don't use set_pte_at when updating protnone  ptes Mel Gorman <mgorman@techsingularity.net> - 2017-02-06 23:30 +0100

csiph-web