From: Bernhard Walle <bwalle@suse.de>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Limit E820 map and /proc/iomem for mem parameter on x86-64
Date: Wed, 11 Jun 2008 17:45:03 +0200 [thread overview]
Message-ID: <20080611174503.3e6b18e8@halley.suse.de> (raw)
In-Reply-To: <20080611153901.GD6450@redhat.com>
* Vivek Goyal [2008-06-11 11:39]:
>
> 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.
Yes, of course, I just don't have time to work full-time on that, so be
a bit patient. :)
Bernhard
--
Bernhard Walle, SUSE LINUX Products GmbH, Architecture Development
next prev parent reply other threads:[~2008-06-11 15:44 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
2008-06-11 15:45 ` Bernhard Walle [this message]
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=20080611174503.3e6b18e8@halley.suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.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