[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20121018150502.3dee7899.akpm@linux-foundation.org>
Date: Thu, 18 Oct 2012 15:05:02 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Will Deacon <will.deacon@....com>
Cc: David Miller <davem@...emloft.net>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"mhocko@...e.cz" <mhocko@...e.cz>,
"kirill@...temov.name" <kirill@...temov.name>,
"aarcange@...hat.com" <aarcange@...hat.com>,
"cmetcalf@...era.com" <cmetcalf@...era.com>,
Steve Capper <Steve.Capper@....com>
Subject: Re: [PATCH v2] mm: thp: Set the accessed flag for old pages on
access fault.
On Wed, 17 Oct 2012 16:54:02 +0100
Will Deacon <will.deacon@....com> wrote:
> On x86 memory accesses to pages without the ACCESSED flag set result in the
> ACCESSED flag being set automatically. With the ARM architecture a page access
> fault is raised instead (and it will continue to be raised until the ACCESSED
> flag is set for the appropriate PTE/PMD).
>
> For normal memory pages, handle_pte_fault will call pte_mkyoung (effectively
> setting the ACCESSED flag). For transparent huge pages, pmd_mkyoung will only
> be called for a write fault.
>
> This patch ensures that faults on transparent hugepages which do not result
> in a CoW update the access flags for the faulting pmd.
Confused. Where is the arm implementation of update_mmu_cache_pmd()?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists