From: Philipp Hachtmann <phacht@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
qiuxishi@huawei.com, dhowells@redhat.com, daeseok.youn@gmail.com,
liuj97@gmail.com, yinghai@kernel.org, zhangyanfei@cn.fujitsu.com,
santosh.shilimkar@ti.com, grygorii.strashko@ti.com,
tangchen@cn.fujitsu.com
Subject: Re: [PATCH V3 2/2] mm/memblock: Add support for excluded memory areas
Date: Tue, 14 Jan 2014 10:42:53 +0100 [thread overview]
Message-ID: <20140114104253.54ea0470@lilie> (raw)
In-Reply-To: <20140113163620.ade5ee9171c5f443a227f8af@linux-foundation.org>
Am Mon, 13 Jan 2014 16:36:20 -0800
schrieb Andrew Morton <akpm@linux-foundation.org>:
> Patch is big. I'll toss this in for some testing but it does look too
> large and late for 3.14. How will this affect your s390 development?
It is needed for s390 bootmem -> memblock transition. The s390 dump
mechanisms cannot be switched to memblock (from using something s390
specific called memory_chunk) without the nomap list.
I'm also working on another enhancement on s390 that will rely on a
clean transition to memblock.
I have written and tested the stuff on top of our local development
tree. And then realised that it does not fit the linux-next tree. So I
converted it to fit linux-next and posted it. Have to maintain two
versions now.
--
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:[~2014-01-14 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 13:03 [PATCH V3 0/2] mm/memblock: Excluded memory, free_all_bootmem Philipp Hachtmann
2014-01-13 13:03 ` [PATCH V3 1/2] mm/nobootmem: free_all_bootmem again Philipp Hachtmann
2014-01-13 13:03 ` [PATCH V3 2/2] mm/memblock: Add support for excluded memory areas Philipp Hachtmann
2014-01-14 0:36 ` Andrew Morton
2014-01-14 9:42 ` Philipp Hachtmann [this message]
2014-01-14 22:01 ` Andrew Morton
2014-01-14 13:17 ` Grygorii Strashko
2014-01-14 14:24 ` Santosh Shilimkar
2014-01-14 18:52 ` Philipp Hachtmann
2014-01-17 18:08 ` Strashko, Grygorii
2014-01-20 8:39 ` Philipp Hachtmann
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=20140114104253.54ea0470@lilie \
--to=phacht@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=daeseok.youn@gmail.com \
--cc=dhowells@redhat.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liuj97@gmail.com \
--cc=qiuxishi@huawei.com \
--cc=santosh.shilimkar@ti.com \
--cc=tangchen@cn.fujitsu.com \
--cc=yinghai@kernel.org \
--cc=zhangyanfei@cn.fujitsu.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