public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wu Fengguang <fengguang.wu@intel.com>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: "Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Chen Liqin" <liqin.chen@sunplusct.com>,
	"Lennox Wu" <lennox.wu@gmail.com>,
	"Ralf Baechle" <ralf@linux-mips.org>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
	"Yinghai Lu" <yinghai@kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Andi Kleen" <andi@firstfloor.org>,
	"Zheng, Shaohui" <shaohui.zheng@intel.com>
Subject: Re: [PATCH 1/3] resources: introduce generic page_is_ram()
Date: Fri, 22 Jan 2010 13:52:17 +0800	[thread overview]
Message-ID: <20100122055217.GA8358@localhost> (raw)
In-Reply-To: <7b6bb4a51001212150h32f62e53ga230b381ce5da126@mail.gmail.com>

On Thu, Jan 21, 2010 at 09:50:01PM -0800, Xiaotian Feng wrote:
> On Fri, Jan 22, 2010 at 1:37 PM, Wu Fengguang <fengguang.wu@intel.com> wrote:
> > On Thu, Jan 21, 2010 at 10:15:50PM -0700, Xiaotian Feng wrote:
> >> On Fri, Jan 22, 2010 at 11:21 AM, Wu Fengguang <fengguang.wu@intel.com> wrote:
> >> > It's based on walk_system_ram_range(), for archs that don't have
> >> > their own page_is_ram().
> >> >
> >> > The static verions in MIPS and SCORE are also made global.
> >> >
> >> > CC: Chen Liqin <liqin.chen@sunplusct.com>
> >> > CC: Lennox Wu <lennox.wu@gmail.com>
> >> > CC: Ralf Baechle <ralf@linux-mips.org>
> >> > CC: Américo Wang <xiyou.wangcong@gmail.com>
> >> > CC: linux-mips@linux-mips.org
> >> > CC: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> >> > CC: Yinghai Lu <yinghai@kernel.org>
> >> > Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
> >> > ---
> >> >  arch/mips/mm/init.c    |    2 +-
> >> >  arch/score/mm/init.c   |    2 +-
> >> >  include/linux/ioport.h |    2 ++
> >> >  kernel/resource.c      |   11 +++++++++++
> >> >  4 files changed, 15 insertions(+), 2 deletions(-)
> >> >
> >> > --- linux-mm.orig/kernel/resource.c     2010-01-22 11:20:34.000000000 +0800
> >> > +++ linux-mm/kernel/resource.c  2010-01-22 11:20:35.000000000 +0800
> >> > @@ -327,6 +327,17 @@ int walk_system_ram_range(unsigned long
> >> >
> >> >  #endif
> >> >
> >> > +#define PAGE_IS_RAM    24
> >> > +static int __is_ram(unsigned long pfn, unsigned long nr_pages, void *arg)
> >> > +{
> >> > +       return PAGE_IS_RAM;
> >> > +}
> >> > +int __attribute__((weak)) page_is_ram(unsigned long pfn)
> >> > +{
> >> > +       return PAGE_IS_RAM == walk_system_ram_range(pfn, 1, NULL, __is_ram);
> >> > +}
> >> > +#undef PAGE_IS_RAM
> >> > +
> >>
> >> I'm not sure, but any build test for powerpc/mips/score?
> >
> > Sorry, no build tests yet:
> >
> >        /bin/sh: score-linux-gcc: command not found
> >
> > I just make the mips/score page_is_ram() non-static and assume that
> > will make it compile.
> >
> >> walk_system_ram_range is defined when CONFIG_ARCH_HAS_WALK_MEMORY is not set.
> >> Is it safe when CONFIG_ARCH_HAS_WALK_MEMORY is set for some powerpc archs?
> >
> > Good question. Grep shows that CONFIG_ARCH_HAS_WALK_MEMORY is only
> > defined for powerpc, and it has its own page_is_ram() as well as
> > walk_system_ram_range().
> >
> > walk_system_ram_range() must be defined somewhere because it is
> > expected to be generic routine: exported and called from both
> > in-kernel and out-of-tree code.
> >
> 
> Yes, powerpc has its own walk_system_ram_range() and page_is_ram() ;-)
> 
> Would it be better if moving the weak attribute page_is_ram() into #if
> !defined(CONFIG_ARCH_HAS_WALK_MEMORY) ?

Only several archs defined page_is_ram(), so that would not be feasible
for doing a _generic_ page_is_ram().

Thanks,
Fengguang

  reply	other threads:[~2010-01-22  5:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22  3:21 [PATCH 0/3] generic hotplug friendly page_is_ram() Wu Fengguang
2010-01-22  3:21 ` [PATCH 1/3] resources: introduce generic page_is_ram() Wu Fengguang
2010-01-22  4:10   ` KAMEZAWA Hiroyuki
2010-01-22  4:20     ` [PATCH 1/3 v3] " Wu Fengguang
2010-01-22  5:15   ` [PATCH 1/3] " Xiaotian Feng
2010-01-22  5:37     ` Wu Fengguang
2010-01-22  5:50       ` Xiaotian Feng
2010-01-22  5:52         ` Wu Fengguang [this message]
2010-01-22  7:51   ` H. Peter Anvin
2010-01-22  8:16     ` [PATCH 1/3 v4] " Wu Fengguang
2010-01-27  0:30       ` Andrew Morton
2010-01-27  3:06         ` Wu Fengguang
2010-02-02  1:01           ` [tip:x86/mm] Move page_is_ram() declaration to mm.h tip-bot for Wu Fengguang
2010-01-22  3:21 ` [PATCH 2/3] x86: remove bios data range from e820 Wu Fengguang
2010-01-22  4:06   ` Wu Fengguang
2010-01-27  0:32   ` Andrew Morton
2010-02-02  1:01   ` [tip:x86/mm] x86: Remove BIOS " tip-bot for Yinghai Lu
2010-01-22  3:21 ` [PATCH 3/3] x86: use the generic page_is_ram() Wu Fengguang
2010-02-02  1:01   ` [tip:x86/mm] x86: Use " tip-bot for Wu Fengguang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100122055217.GA8358@localhost \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lennox.wu@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=liqin.chen@sunplusct.com \
    --cc=mingo@redhat.com \
    --cc=ralf@linux-mips.org \
    --cc=shaohui.zheng@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    --cc=xtfeng@gmail.com \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox