From: Amerigo Wang <amwang@redhat.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, tony.luck@intel.com,
linux-ia64@vger.kernel.org, linux-mm@kvack.org,
Neil Horman <nhorman@redhat.com>,
Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, bernhard.walle@gmx.de,
Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [Patch 8/8] kexec: allow to shrink reserved memory
Date: Wed, 19 Aug 2009 10:41:13 +0800 [thread overview]
Message-ID: <4A8B6649.3080103@redhat.com> (raw)
In-Reply-To: <20090819085703.ccf9992a.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> On Tue, 18 Aug 2009 18:35:32 +0800
> Amerigo Wang <amwang@redhat.com> wrote:
>
>
>> KAMEZAWA Hiroyuki wrote:
>>
>>> On Tue, 18 Aug 2009 14:31:23 +0800
>>> Amerigo Wang <amwang@redhat.com> wrote:
>>>
>>>
>>>>> It's hidden from the system before mem_init() ?
>>>>>
>>>>>
>>>>>
>>>> Not sure, but probably yes. It is reserved in setup_arch() which is
>>>> before mm_init() which calls mem_init().
>>>>
>>>> Do you have any advice to free that reserved memory after boot? :)
>>>>
>>>>
>>>>
>>> Let's see arch/x86/mm/init.c::free_initmem()
>>>
>>> Maybe it's all you want.
>>>
>>> - ClearPageReserved()
>>> - init_page_count()
>>> - free_page()
>>> - totalram_pages++
>>>
>>>
>> Just FYI: calling ClearPageReserved() caused an oops: "Unable to handle
>> paging request".
>>
>> I am trying to figure out why...
>>
>>
> Hmm...then....memmap is not there.
> pfn_valid() check will help you. What arch ? x86-64 ?
>
Hmm, yes, x86_64, but this code is arch-independent, I mean it should
work or not work on all arch, no?
So I am afraid we need to use other API to free it...
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>
next prev parent reply other threads:[~2009-08-19 2:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090812081731.5757.25254.sendpatchset@localhost.localdomain>
[not found] ` <20090812081906.5757.39417.sendpatchset@localhost.localdomain>
[not found] ` <m1bpmk8l1g.fsf@fess.ebiederm.org>
2009-08-13 3:32 ` Amerigo Wang
2009-08-13 6:18 ` Eric W. Biederman
2009-08-13 8:23 ` Amerigo Wang
2009-08-14 22:17 ` Eric W. Biederman
2009-08-17 9:50 ` Amerigo Wang
2009-08-18 0:29 ` KAMEZAWA Hiroyuki
2009-08-18 6:31 ` Amerigo Wang
2009-08-18 8:25 ` KAMEZAWA Hiroyuki
2009-08-18 8:51 ` Amerigo Wang
2009-08-18 10:35 ` Amerigo Wang
2009-08-18 23:57 ` KAMEZAWA Hiroyuki
2009-08-19 2:41 ` Amerigo Wang [this message]
2009-08-19 8:13 ` KAMEZAWA Hiroyuki
2009-08-19 10:47 ` Amerigo Wang
2009-08-20 9:15 ` Amerigo Wang
2009-08-21 0:34 ` KAMEZAWA Hiroyuki
2009-08-21 1:59 ` Amerigo Wang
2009-08-21 2:03 ` KAMEZAWA Hiroyuki
2009-08-21 2:47 ` Amerigo Wang
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=4A8B6649.3080103@redhat.com \
--to=amwang@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=avorontsov@ru.mvista.com \
--cc=bernhard.walle@gmx.de \
--cc=ebiederm@xmission.com \
--cc=fenghua.yu@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nhorman@redhat.com \
--cc=tony.luck@intel.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