Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760228Ab2JYTv1 (ORCPT ); Thu, 25 Oct 2012 15:51:27 -0400 Received: from zene.cmpxchg.org ([85.214.230.12]:59917 "EHLO zene.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759761Ab2JYTvZ (ORCPT ); Thu, 25 Oct 2012 15:51:25 -0400 Date: Thu, 25 Oct 2012 15:51:10 -0400 From: Johannes Weiner To: Will Deacon Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, mhocko@suse.cz, peterz@infradead.org, akpm@linux-foundation.org, Chris Metcalf , "Kirill A. Shutemov" , Andrea Arcangeli Subject: Re: [PATCH v3] mm: thp: Set the accessed flag for old pages on access fault. Message-ID: <20121025195110.GA4771@cmpxchg.org> References: <1351183471-14710-1-git-send-email-will.deacon@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1351183471-14710-1-git-send-email-will.deacon@arm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1732 Lines: 36 On Thu, Oct 25, 2012 at 05:44:31PM +0100, Will Deacon 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. > > Cc: Chris Metcalf > Cc: Kirill A. Shutemov > Cc: Andrea Arcangeli > Signed-off-by: Will Deacon Acked-by: Johannes Weiner > Ok chaps, I rebased this thing onto today's next (which basically > necessitated a rewrite) so I've reluctantly dropped my acks and kindly > ask if you could eyeball the new code, especially where the locking is > concerned. In the numa code (do_huge_pmd_prot_none), Peter checks again > that the page is not splitting, but I can't see why that is required. I don't either. If the thing was splitting when the fault happened, that path is not taken. And the locked pmd_same() check should rule out splitting setting in after testing pmd_trans_huge_splitting(). Peter? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/