Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753494Ab3G0GZS (ORCPT ); Sat, 27 Jul 2013 02:25:18 -0400 Received: from mail-lb0-f178.google.com ([209.85.217.178]:49795 "EHLO mail-lb0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752725Ab3G0GZP (ORCPT ); Sat, 27 Jul 2013 02:25:15 -0400 Date: Sat, 27 Jul 2013 10:25:12 +0400 From: Cyrill Gorcunov To: Andy Lutomirski Cc: Linux MM , LKML , Pavel Emelyanov , Andrew Morton , Matt Mackall , Xiao Guangrong , Marcelo Tosatti , KOSAKI Motohiro , Stephen Rothwell Subject: Re: [PATCH] mm: Save soft-dirty bits on file pages Message-ID: <20130727062512.GC8508@moon> References: <20130726201807.GJ8661@moon> <20130726211844.GB8508@moon> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1062 Lines: 21 On Fri, Jul 26, 2013 at 02:36:51PM -0700, Andy Lutomirski wrote: > >> Unless I'm misunderstanding this, it's saving the bit in the > >> non-present PTE. This sounds wrong -- what happens if the entire pmd > > > > It's the same as encoding pgoff in pte entry (pte is not present), > > but together with pgoff we save soft-bit status, later on #pf we decode > > pgoff and restore softbit back if it was there, pte itself can't disappear > > since it holds pgoff information. > > Isn't that only the case for nonlinear mappings? Andy, I'm somehow lost, pte either exist with file encoded, either not, when pud/ptes are zapped and any access to it should cause #pf pointing kernel to read/write data from file to a page, if it happens on write the pte is obtaining dirty bit (which always set together with soft bit). -- 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/