Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754083AbYLRWP3 (ORCPT ); Thu, 18 Dec 2008 17:15:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751958AbYLRWPQ (ORCPT ); Thu, 18 Dec 2008 17:15:16 -0500 Received: from mga01.intel.com ([192.55.52.88]:57495 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750746AbYLRWPO (ORCPT ); Thu, 18 Dec 2008 17:15:14 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.36,245,1228118400"; d="scan'208";a="415697666" Date: Thu, 18 Dec 2008 14:15:13 -0800 From: "Pallipadi, Venkatesh" To: Nick Piggin Cc: "Pallipadi, Venkatesh" , "mingo@elte.hu" , "tglx@linutronix.de" , "hpa@zytor.com" , "akpm@linux-foundation.org" , "hugh@veritas.com" , "arjan@infradead.org" , "jbarnes@virtuousgeek.org" , "rdreier@cisco.com" , "jeremy@goop.org" , "linux-kernel@vger.kernel.org" , "Siddha, Suresh B" Subject: Re: [patch 2/7] x86 PAT: Add follow_pfnmp_pte routine to help tracking pfnmap pages - v3 Message-ID: <20081218221512.GB3331@linux-os.sc.intel.com> References: <20081218194126.963894000@intel.com> <20081218194617.247280000@intel.com> <20081218213112.GE10681@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081218213112.GE10681@wotan.suse.de> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1047 Lines: 24 On Thu, Dec 18, 2008 at 01:31:12PM -0800, Nick Piggin wrote: > On Thu, Dec 18, 2008 at 11:41:28AM -0800, venkatesh.pallipadi@intel.com wrote: > > Add a generic interface to follow pfn in a pfnmap vma range. This is used by > > one of the subsequent x86 PAT related patch to keep track of memory types > > for vma regions across vma copy and free. > > > > Signed-off-by: Venkatesh Pallipadi > > Signed-off-by: Suresh Siddha > > Can you please reuse follow_phys for this? (preferably use the same API > even if it requires some modification, otherwise if not possible, then > at least can you implement a common core for both APIs). > Yes. Hadn't noticed the presence of follow_phys before. Will send a patch to handle this. Thanks, Venki -- 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/