From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: kosaki.motohiro@jp.fujitsu.com,
Linux Memory Management <linux-mm@kvack.org>,
linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] vmalloc: Add __get_vm_area_caller()
Date: Wed, 11 Feb 2009 17:22:47 +0900 (JST) [thread overview]
Message-ID: <20090211171804.7021.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20090211044854.969CEDDDA9@ozlabs.org>
> We have get_vm_area_caller() and __get_vm_area() but not __get_vm_area_caller()
>
> On powerpc, I use __get_vm_area() to separate the ranges of addresses given
> to vmalloc vs. ioremap (various good reasons for that) so in order to be
> able to implement the new caller tracking in /proc/vmallocinfo, I need
> a "_caller" variant of it.
>
> Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
It seems reasonable reason and this patch looks good to me :)
Reviewed-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
> I want to put into powerpc-next patches relying into that, so if the
> patch is ok with you guys, can I stick it in powerpc.git ?
hm.
Generally, all MM patch should merge into -mm tree at first.
but I don't think this patch have conflict risk.
Andrew, What do you think?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-02-11 8:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-11 4:48 Benjamin Herrenschmidt
2009-02-11 8:22 ` KOSAKI Motohiro [this message]
2009-02-11 22:45 ` Andrew Morton
2009-02-11 23:53 ` KOSAKI Motohiro
2009-02-12 0:11 ` Benjamin Herrenschmidt
2009-02-12 0:11 ` Benjamin Herrenschmidt
2009-02-12 0:11 ` Benjamin Herrenschmidt
2009-02-12 0:11 ` Benjamin Herrenschmidt
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=20090211171804.7021.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@ozlabs.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