From: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
To: "'linux@arm.linux.org.uk'" <linux@arm.linux.org.uk>,
"'santosh.shilimkar@ti.com'" <santosh.shilimkar@ti.com>,
"'grant.likely@linaro.org'" <grant.likely@linaro.org>,
"'robh@kernel.org'" <robh@kernel.org>,
"'akpm@linux-foundation.org'" <akpm@linux-foundation.org>,
"'m.szyprowski@samsung.com'" <m.szyprowski@samsung.com>,
"'lauraa@codeaurora.org'" <lauraa@codeaurora.org>,
"'linux-arm-kernel@lists.infradead.org'"
<linux-arm-kernel@lists.infradead.org>,
"'linux-kernel@vger.kernel.org'"
<linux-kernel@vger.kernel.org>"'m.szyprowski@samsung.com'"
<m.szyprowski@samsung.com>"'akpm@linux-foundation.org'"
<akpm@linux-foundation.org>,
"'iamjoonsoo.kim@lge.com'" <iamjoonsoo.kim@lge.com>,
"'mina86@mina86.com'" <mina86@mina86.com>,
"'aneesh.kumar@linux.vnet.ibm.com'"
<aneesh.kumar@linux.vnet.ibm.com>"'lauraa@codeaurora.org'"
<lauraa@codeaurora.org>, "'gioh.kim@lge.com'" <gioh.kim@lge.com>,
"'michael.opdenacker@free-electrons.com'"
<michael.opdenacker@free-electrons.com>,
"'akinobu.mita@gmail.com'" <akinobu.mita@gmail.com>,
"'linux-mm@kvack.org'"
<linux-mm@kvack.org>"'linux-kernel@vger.kernel.org'"
<linux-kernel@vger.kernel.org>
Subject: free initrd / cma pages problems with memblock
Date: Wed, 3 Sep 2014 17:57:57 +0800 [thread overview]
Message-ID: <35FD53F367049845BC99AC72306C23D103CDBFBFB00B@CNBJMBX05.corpusers.net> (raw)
Hi
I found the freed reserved memory by free_initrd_mem( ) and cma_activate_area( )
Are still marked as reserved in /sys/kernel/debug/memblock/reserved .
I think This is not correct and not suitable for memory debug,
Why not also call memblock_free during these functions?
So that /sys/kernel/debug/memblock/reserved only mark really reserved memory as reserved .
Thanks.
--
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>
reply other threads:[~2014-09-03 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=35FD53F367049845BC99AC72306C23D103CDBFBFB00B@CNBJMBX05.corpusers.net \
--to=yalin.wang@sonymobile.com \
--cc=akpm@linux-foundation.org \
--cc=grant.likely@linaro.org \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=robh@kernel.org \
--cc=santosh.shilimkar@ti.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