linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Simon Jeons <simon.jeons@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: linux-mm@kvack.org, Andi Kleen <andi@firstfloor.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shaohua Li <shaohua.li@intel.com>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Mel Gorman <mgorman@suse.de>, Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH 0/2] pageattr fixes for pmd/pte_present
Date: Thu, 10 Jan 2013 01:42:09 -0600	[thread overview]
Message-ID: <1357803729.6568.12.camel@kernel.cn.ibm.com> (raw)
In-Reply-To: <1355767224-13298-1-git-send-email-aarcange@redhat.com>

On Mon, 2012-12-17 at 19:00 +0100, Andrea Arcangeli wrote:
> Hi,
> 
> I got a report for a minor regression introduced by commit
> 027ef6c87853b0a9df53175063028edb4950d476.
> 
> So the problem is, pageattr creates kernel pagetables (pte and pmds)
> that breaks pte_present/pmd_present and the patch above exposed this
> invariant breakage for pmd_present.
> 
> The same problem already existed for the pte and pte_present and it
> was fixed by commit 660a293ea9be709b893d371fbc0328fcca33c33a (if it
> wasn't for that commit, it wouldn't even be a regression). That fix
> avoids the pagefault to use pte_present. I could follow through by
> stopping using pmd_present/pmd_huge too.
> 
> However I think it's more robust to fix pageattr and to clear the
> PSE/GLOBAL bitflags too in addition to the present bitflag. So the
> kernel page fault can keep using the regular
> pte_present/pmd_present/pmd_huge.
> 
> The confusion arises because _PAGE_GLOBAL and _PAGE_PROTNONE are
> sharing the same bit, and in the pmd case we pretend _PAGE_PSE to be
> set only in present pmds (to facilitate split_huge_page final tlb
> flush).

Hi all,

One offline question.

Why free pages should map to kernel virtual address in function
isolate_freepages? If you said that those pages are about to be used as
migration targets, it's splitting a free page but those pages are about
to be used for copying data to, then why kernel need to access these
pages? These target pages are isolated buddy pages and they will be the
migration targets of normal processes' pages, why kernel need to access
them? 

> 
> Andrea Arcangeli (2):
>   Revert "x86, mm: Make spurious_fault check explicitly check the
>     PRESENT bit"
>   pageattr: prevent PSE and GLOABL leftovers to confuse pmd/pte_present
>     and pmd_huge
> 
>  arch/x86/mm/fault.c    |    8 +------
>  arch/x86/mm/pageattr.c |   50 +++++++++++++++++++++++++++++++++++++++++++++--
>  2 files changed, 48 insertions(+), 10 deletions(-)
> 
> --
> 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>


--
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>

      parent reply	other threads:[~2013-01-10  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17 18:00 Andrea Arcangeli
2012-12-17 18:00 ` [PATCH 1/2] Revert "x86, mm: Make spurious_fault check explicitly check the PRESENT bit" Andrea Arcangeli
2012-12-17 18:17   ` H. Peter Anvin
2012-12-17 18:35     ` Andrea Arcangeli
2012-12-17 18:00 ` [PATCH 2/2] pageattr: prevent PSE and GLOABL leftovers to confuse pmd/pte_present and pmd_huge Andrea Arcangeli
2013-01-10  7:59   ` Simon Jeons
2013-01-06  2:59 ` [PATCH 0/2] pageattr fixes for pmd/pte_present Simon Jeons
2013-01-07 21:53   ` Andrew Morton
2013-01-07 21:55     ` H. Peter Anvin
2013-01-08 12:25       ` Andrea Arcangeli
2013-01-10  7:42 ` Simon Jeons [this message]

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=1357803729.6568.12.camel@kernel.cn.ibm.com \
    --to=simon.jeons@gmail.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hpa@linux.intel.com \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=shaohua.li@intel.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