From: Vivek Goyal <vgoyal@redhat.com>
To: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Bernhard Walle <bwalle@suse.de>
Subject: Re: [PATCH] Limit E820 map and /proc/iomem for mem parameter on x86-64
Date: Wed, 11 Jun 2008 11:39:01 -0400 [thread overview]
Message-ID: <20080611153901.GD6450@redhat.com> (raw)
In-Reply-To: <20080610215325.GA20673@suse.de>
On Tue, Jun 10, 2008 at 11:53:25PM +0200, Bernhard Walle wrote:
> This patch tries to unify the behaviour of i386 and x86-64 when parsing
> the memory (mem/memmap) parameter of the kernel command line:
>
> On i386, the view was limited (i.e. the actual view was presented).
> On x86-64, the view was full (i.e. the BIOS view was presented).
>
> This patch moves the limit_regions() function and the print_memory_map()
> function to a new file e820.c, shared between the two x86 flavours. Then
> it adds calls to limit_regions() in 64 bit code.
>
> I gave the patch a bit testing. However, it's not for merging, it's just
> to get early feedback to see if that goes into the right direction.
>
>
I would like to have consistent behavior of /proc/iomem across i386
and x86_64, so this sounds like right direction to me.
Also I would like to have another interface (say /proc/iomem_kernel)which
actually gets modified based on the user specified options. So effectively we
can have both the views. BIOS view and user defined view.
As discussed on kexec mailing list, it helps kexec and kdump operation.
In the case of kexec, we want to know the actual resources present in
the system so that new kernel can see it (Irrespective of the fact
what first kernel was actually using).
In case of kdump, we want to see truncated view so that we don't end
up capturing the contents of memory not being used by kernel.
Thanks
Vivek
next prev parent reply other threads:[~2008-06-11 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 21:53 [PATCH] Limit E820 map and /proc/iomem for mem parameter on x86-64 Bernhard Walle
2008-06-11 15:39 ` Vivek Goyal [this message]
2008-06-11 15:45 ` Bernhard Walle
2008-06-13 1:43 ` Yinghai Lu
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=20080611153901.GD6450@redhat.com \
--to=vgoyal@redhat.com \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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