All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Mel Gorman <mgorman@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>, Peter Anvin <hpa@zytor.com>,
	Ingo Molnar <mingo@kernel.org>,
	Steven Noonan <steven@uplinklabs.net>,
	Rik van Riel <riel@redhat.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Linux-MM <linux-mm@kvack.org>, Linux-X86 <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] x86: Define _PAGE_NUMA with unused physical address bits PMD and PTE levels
Date: Mon, 07 Apr 2014 10:37:55 -0700	[thread overview]
Message-ID: <5342E273.4070308@intel.com> (raw)
In-Reply-To: <1396883443-11696-3-git-send-email-mgorman@suse.de>

On 04/07/2014 08:10 AM, Mel Gorman wrote:
> +/*
> + * Software bits ignored by the page table walker
> + * At the time of writing, different levels have bits that are ignored. Due
> + * to physical address limitations, bits 52:62 should be ignored for the PMD
> + * and PTE levels and are available for use by software. Be aware that this
> + * may change if the physical address space expands.
> + */
> +#define _PAGE_BIT_NUMA		62

Doesn't moving it up to the high bits break pte_modify()'s assumptions?
 I was thinking of this nugget from change_pte_range():

	ptent = ptep_modify_prot_start(mm, addr, pte);
        if (pte_numa(ptent))
        	ptent = pte_mknonnuma(ptent);
	ptent = pte_modify(ptent, newprot);

pte_modify() pulls off all the high bits out of 'ptent' and only adds
them back if they're in newprot (which as far as I can tell comes from
the VMA).  So I _think_ it'll axe the _PAGE_NUMA out of 'ptent'.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <dave.hansen@intel.com>
To: Mel Gorman <mgorman@suse.de>,
	Linus Torvalds <torvalds@linux-foundation.org>
Cc: Cyrill Gorcunov <gorcunov@gmail.com>, Peter Anvin <hpa@zytor.com>,
	Ingo Molnar <mingo@kernel.org>,
	Steven Noonan <steven@uplinklabs.net>,
	Rik van Riel <riel@redhat.com>,
	David Vrabel <david.vrabel@citrix.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Linux-MM <linux-mm@kvack.org>, Linux-X86 <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] x86: Define _PAGE_NUMA with unused physical address bits PMD and PTE levels
Date: Mon, 07 Apr 2014 10:37:55 -0700	[thread overview]
Message-ID: <5342E273.4070308@intel.com> (raw)
In-Reply-To: <1396883443-11696-3-git-send-email-mgorman@suse.de>

On 04/07/2014 08:10 AM, Mel Gorman wrote:
> +/*
> + * Software bits ignored by the page table walker
> + * At the time of writing, different levels have bits that are ignored. Due
> + * to physical address limitations, bits 52:62 should be ignored for the PMD
> + * and PTE levels and are available for use by software. Be aware that this
> + * may change if the physical address space expands.
> + */
> +#define _PAGE_BIT_NUMA		62

Doesn't moving it up to the high bits break pte_modify()'s assumptions?
 I was thinking of this nugget from change_pte_range():

	ptent = ptep_modify_prot_start(mm, addr, pte);
        if (pte_numa(ptent))
        	ptent = pte_mknonnuma(ptent);
	ptent = pte_modify(ptent, newprot);

pte_modify() pulls off all the high bits out of 'ptent' and only adds
them back if they're in newprot (which as far as I can tell comes from
the VMA).  So I _think_ it'll axe the _PAGE_NUMA out of 'ptent'.

  parent reply	other threads:[~2014-04-07 19:58 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 15:10 [RFC PATCH 0/3] Use an alternative to _PAGE_PROTNONE for _PAGE_NUMA Mel Gorman
2014-04-07 15:10 ` Mel Gorman
2014-04-07 15:10 ` [PATCH 1/3] x86: Require x86-64 for automatic NUMA balancing Mel Gorman
2014-04-07 15:10   ` Mel Gorman
2014-04-07 15:10 ` [PATCH 2/3] x86: Define _PAGE_NUMA with unused physical address bits PMD and PTE levels Mel Gorman
2014-04-07 15:10   ` Mel Gorman
2014-04-07 15:32   ` David Vrabel
2014-04-07 15:32     ` David Vrabel
2014-04-07 15:49     ` Mel Gorman
2014-04-07 15:49       ` Mel Gorman
2014-04-07 16:19       ` Cyrill Gorcunov
2014-04-07 16:19         ` Cyrill Gorcunov
2014-04-07 18:28         ` Mel Gorman
2014-04-07 18:28           ` Mel Gorman
2014-04-07 19:16           ` Cyrill Gorcunov
2014-04-07 19:16             ` Cyrill Gorcunov
2014-04-07 19:27           ` H. Peter Anvin
2014-04-07 19:27             ` H. Peter Anvin
2014-04-07 19:36             ` Cyrill Gorcunov
2014-04-07 19:36               ` Cyrill Gorcunov
2014-04-07 19:42               ` H. Peter Anvin
2014-04-07 19:42                 ` H. Peter Anvin
2014-04-07 21:25                 ` Mel Gorman
2014-04-07 21:25                   ` Mel Gorman
2014-04-08  4:04                   ` Steven Noonan
2014-04-08  4:04                     ` Steven Noonan
2014-04-08 15:16                     ` H. Peter Anvin
2014-04-08 15:16                       ` H. Peter Anvin
2014-04-08 16:02                       ` Konrad Rzeszutek Wilk
2014-04-08 16:02                         ` Konrad Rzeszutek Wilk
2014-04-08 16:16                         ` H. Peter Anvin
2014-04-08 16:16                           ` H. Peter Anvin
2014-04-08 16:47                           ` Mel Gorman
2014-04-08 16:47                             ` Mel Gorman
2014-04-08 16:50                           ` David Vrabel
2014-04-08 16:50                             ` David Vrabel
2014-04-08 16:51                         ` Mel Gorman
2014-04-08 16:51                           ` Mel Gorman
2014-04-09 15:18                           ` Konrad Rzeszutek Wilk
2014-04-09 15:18                             ` Konrad Rzeszutek Wilk
2014-04-09 15:39                             ` Mel Gorman
2014-04-09 15:39                               ` Mel Gorman
2014-04-08 20:51                       ` Steven Noonan
2014-04-08 20:51                         ` Steven Noonan
2014-04-08 20:59                         ` H. Peter Anvin
2014-04-08 20:59                           ` H. Peter Anvin
2014-04-09 15:04                           ` Konrad Rzeszutek Wilk
2014-04-09 15:04                             ` Konrad Rzeszutek Wilk
2014-04-09 15:09                             ` Peter Zijlstra
2014-04-09 15:09                               ` Peter Zijlstra
2014-04-08  9:31               ` David Vrabel
2014-04-08  9:31                 ` David Vrabel
2014-04-07 21:19             ` Mel Gorman
2014-04-07 21:19               ` Mel Gorman
2014-04-07 17:37   ` Dave Hansen [this message]
2014-04-07 17:37     ` Dave Hansen
2014-04-07 15:10 ` [PATCH 3/3] mm: Allow FOLL_NUMA on FOLL_FORCE Mel Gorman
2014-04-07 15:10   ` Mel Gorman

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=5342E273.4070308@intel.com \
    --to=dave.hansen@intel.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david.vrabel@citrix.com \
    --cc=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.com \
    --cc=steven@uplinklabs.net \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.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.