From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932465AbVHIIi6 (ORCPT ); Tue, 9 Aug 2005 04:38:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932467AbVHIIi6 (ORCPT ); Tue, 9 Aug 2005 04:38:58 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:10655 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S932465AbVHIIi6 (ORCPT ); Tue, 9 Aug 2005 04:38:58 -0400 Subject: Re: [RFC][patch 0/2] mm: remove PageReserved From: Arjan van de Ven To: Russell King Cc: Nick Piggin , ncunningham@cyclades.com, Daniel Phillips , Linux Kernel Mailing List , Linux Memory Management , Hugh Dickins , Linus Torvalds , Andrew Morton , Andrea Arcangeli , Benjamin Herrenschmidt In-Reply-To: <20050809080853.A25492@flint.arm.linux.org.uk> References: <42F57FCA.9040805@yahoo.com.au> <200508090710.00637.phillips@arcor.de> <1123562392.4370.112.camel@localhost> <42F83849.9090107@yahoo.com.au> <20050809080853.A25492@flint.arm.linux.org.uk> Content-Type: text/plain Date: Tue, 09 Aug 2005 10:38:39 +0200 Message-Id: <1123576719.3839.13.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.2 (2.2.2-5) Content-Transfer-Encoding: 7bit X-Spam-Score: 2.9 (++) X-Spam-Report: SpamAssassin version 3.0.4 on pentafluge.infradead.org summary: Content analysis details: (2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [80.57.133.107 listed in dnsbl.sorbs.net] 2.8 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org [] X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2005-08-09 at 08:08 +0100, Russell King wrote: > On Tue, Aug 09, 2005 at 02:59:53PM +1000, Nick Piggin wrote: > > That would work for swsusp, but there are other users that want to > > know if a struct page is valid ram (eg. ioremap), so in that case > > swsusp would not be able to mess with the flag. > > The usage of "valid ram" here is confusing - that's not what PageReserved > is all about. It's about valid RAM which is managed by method other > than the usual page counting. Non-reserved RAM is also valid RAM, but > is managed by the kernel in the usual way. > > The former is available for remap_pfn_range and ioremap, the latter is > not. > > On the other hand, the validity of an apparant RAM address can only be > tested using its pfn with pfn_valid(). > > Can we straighten out the terminology so it's less confusing please? > and..... can we make a general page_is_ram() function that does what it says? on x86 it can go via the e820 table, other architectures can do whatever they need....