From: Amerigo Wang <xiyou.wangcong@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/4] kcore: cleanup and fix bahavior to find physcal memory range v2
Date: Wed, 22 Jul 2009 13:52:32 +0800 [thread overview]
Message-ID: <20090722055232.GA6281@cr0.nay.redhat.com> (raw)
In-Reply-To: <20090722140613.0a751811.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, Jul 22, 2009 at 02:06:13PM +0900, KAMEZAWA Hiroyuki wrote:
>I'm sorry I can't find who should be in CC.
>
Just keep the original CC's, or run scripts/get_maintainer.pl -f fs/proc/kcore.c.
:-)
>This includes some amounts changes to arch-specici code,
>but very special codes for kcore. Can I test this in -mm if no objections ?
>
>Now, /proc/kcore 's physical memory information is set up at boot
>via kclist_add(). But it's not updated at memory hotplug etc and
>it can include much memory holes. This patch is for generatinc /proc/kcore
>based on memory management information maintained by the kernel.
>
> For usual archs, /proc/iomem is used
> For ppc, lmb information will be used.
>
This is a good idea!
prev parent reply other threads:[~2009-07-22 5:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 5:06 [PATCH 0/4] kcore: cleanup and fix bahavior to find physcal memory range v2 KAMEZAWA Hiroyuki
2009-07-22 5:07 ` [PATCH 1/4] kcore: clean up to use generic list ops KAMEZAWA Hiroyuki
2009-07-22 5:53 ` Amerigo Wang
2009-07-22 5:08 ` [PATCH 2/4] kcore: add kclist type KAMEZAWA Hiroyuki
2009-07-22 6:00 ` Amerigo Wang
2009-07-22 6:05 ` KAMEZAWA Hiroyuki
2009-07-22 5:10 ` [PATCH 3/4] kcore: build physical memory direct map information in proper way KAMEZAWA Hiroyuki
2009-07-22 6:09 ` Amerigo Wang
2009-07-22 6:08 ` KAMEZAWA Hiroyuki
2009-07-22 5:12 ` [PATCH 4/4] kcore: remove noise from walk_memory_resource KAMEZAWA Hiroyuki
2009-07-22 6:21 ` Amerigo Wang
2009-07-22 6:22 ` KAMEZAWA Hiroyuki
2009-07-22 6:29 ` Amerigo Wang
2009-07-22 5:52 ` Amerigo Wang [this message]
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=20090722055232.GA6281@cr0.nay.redhat.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.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