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>,
xiyou.wangcong@gmail.com, akpm@linux-foundation.org
Subject: Re: [PATCH 0/6] kcore clean up and enhance
Date: Wed, 12 Aug 2009 17:43:09 +0800 [thread overview]
Message-ID: <20090812094309.GB5929@cr0.nay.redhat.com> (raw)
In-Reply-To: <20090806192416.4f94be76.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Aug 06, 2009 at 07:24:16PM +0900, KAMEZAWA Hiroyuki wrote:
>
>This patch set is for /proc/kcore. By this,
>
> - many per-arch hooks are removed.
>
> - /proc/kcore will know really valid physical memory area.
>
> - /proc/kcore will be aware of memory hotplug.
>
> - /proc/kcore will be architecture independent i.e.
> if an arch supports CONFIG_MMU, it can use /proc/kcore.
> (if the arch uses usual memory layout.)
Hi, this version looks fine for me, I can't spot any obvious
mistakes now.
I would like to see these patches merged into -mm, so that
I can test the whole stuff about /proc/kcore.
Andrew, could you take these?
Thanks!
>
>BTW, I'll be on small trip from Aug/11 to Aug/17. So, my rtt may be
>bad in the next week.
Have a good trip! :)
next prev parent reply other threads:[~2009-08-12 9:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 10:24 KAMEZAWA Hiroyuki
2009-08-06 10:26 ` [PATCH 1/6] kcore: use usual list for kclist KAMEZAWA Hiroyuki
2009-08-06 10:27 ` [PATCH 2/6] kcore: add kclist type KAMEZAWA Hiroyuki
2009-08-06 10:29 ` [PATCH 3/6] kcore regiter vmalloc area in generic way KAMEZAWA Hiroyuki
2009-08-06 10:30 ` [PATCH 4/6] kcore register text " KAMEZAWA Hiroyuki
2009-08-06 10:32 ` [PATCH 5/6] walk sytem ram range KAMEZAWA Hiroyuki
2009-08-06 10:33 ` [PATCH 6/6] kcore use registerd physmem information KAMEZAWA Hiroyuki
2009-08-12 9:43 ` Amerigo Wang [this message]
2009-08-17 2:50 ` [PATCH 0/6] kcore clean up and enhance KAMEZAWA Hiroyuki
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=20090812094309.GB5929@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
all inboxes | Powered by JetHome®