From: Dave Hansen <haveblue@us.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Thomas Q Klein <TKLEIN@de.ibm.com>,
ossthema@linux.vnet.ibm.com,
Jan-Bernd Themann <THEMANN@de.ibm.com>, Greg KH <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>, apw <apw@uk.ibm.com>,
linuxppc-dev@ozlabs.org, Christoph Raisch <RAISCH@de.ibm.com>,
netdev <netdev@vger.kernel.org>,
tklein@linux.ibm.com
Subject: Re: [PATCH] drivers/base: export gpl (un)register_memory_notifier
Date: Thu, 14 Feb 2008 09:38:45 -0800 [thread overview]
Message-ID: <1203010725.19205.44.camel@nimitz.home.sr71.net> (raw)
In-Reply-To: <1203010575.12312.6.camel@dyn9047017100.beaverton.ibm.com>
On Thu, 2008-02-14 at 09:36 -0800, Badari Pulavarty wrote:
>
> I am not sure what you are trying to do with walk_memory_resource().
> The
> behavior is different on ppc64. Hotplug memory usage assumes that all
> the memory resources (all system memory, not just IOMEM) are
> represented
> in /proc/iomem. Its the case with i386 and ia64. But on ppc64 is
> contains ONLY iomem related. Paulus didn't want to export all the
> system
> memory into /proc/iomem on ppc64. So I had to workaround by providing
> arch-specific walk_memory_resource() function for ppc64.
OK, let's use that one.
-- Dave
next prev parent reply other threads:[~2008-02-14 17:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 16:24 [PATCH] drivers/base: export gpl (un)register_memory_notifier Jan-Bernd Themann
2008-02-11 16:47 ` Dave Hansen
2008-02-13 15:17 ` Jan-Bernd Themann
2008-02-13 17:05 ` Dave Hansen
2008-02-14 8:46 ` Christoph Raisch
2008-02-14 17:12 ` Dave Hansen
2008-02-14 17:36 ` Badari Pulavarty
2008-02-14 17:38 ` Dave Hansen [this message]
2008-02-15 13:22 ` Christoph Raisch
2008-02-15 16:55 ` Dave Hansen
2008-02-18 9:56 ` Jan-Bernd Themann
2008-02-18 10:00 ` Jan-Bernd Themann
2008-02-20 18:14 ` Dave Hansen
2008-02-11 16:50 ` Dave Hansen
2008-02-12 18:04 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2008-02-11 15:57 Jan-Bernd Themann
2008-02-11 16:02 ` Sam Ravnborg
2008-02-11 16:04 ` Dave Hansen
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=1203010725.19205.44.camel@nimitz.home.sr71.net \
--to=haveblue@us.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=THEMANN@de.ibm.com \
--cc=TKLEIN@de.ibm.com \
--cc=apw@uk.ibm.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=ossthema@linux.vnet.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=tklein@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).