[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A82182C.1080501@redhat.com>
Date: Wed, 12 Aug 2009 09:17:32 +0800
From: Amerigo Wang <amwang@...hat.com>
To: "Eric W. Biederman" <ebiederm@...ssion.com>
CC: linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org,
Neil Horman <nhorman@...hat.com>,
Andi Kleen <andi@...stfloor.org>, akpm@...ux-foundation.org,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [RFC Patch 1/2] kexec: show memory info in /proc/iomem
Eric W. Biederman wrote:
> Amerigo Wang <amwang@...hat.com> writes:
>
>
>> This patch implements showing kexec memory area via /proc/iomem.
>> For example, with this patch we can see:
>>
>> # cat /proc/iomem
>> ...
>> 00100000-7ffeffff : System RAM
>> 01000000-012e1424 : Kernel code
>> 012e1425-015f1aff : Kernel data
>> 0166b000-01b4b88f : Kernel bss
>> 02000000-083fffff : Crash kernel
>> 02000000-028fffff : Used
>> 02900000-083fffff : Unused
>> ...
>>
>> So that user can know how much memory the kernel uses for crash kernel.
>>
>
> Nacked-by: "Eric W. Biederman" <ebiederm@...ssion.com>
>
> We can inspect the image we are going to load to get this information.
> In fact /sbin/kexec already inspects the image we are going to load
> to get this information. Putting this in the kernel adds kernel
> complexity for no gain.
>
/sbin/kexec is supported to know this, of course. But this is not for
/sbin/kexec, this is for user (or other programs) to observe the memory
information, so that he can know the memory he reserved is too much or not.
Without this, it is a little hard to use patch 2/2.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists