mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yinghai.lu@amd.com>
To: "Andi Kleen" <ak@muc.de>, yhlu <yinghailu@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	Horms <horms@verge.net.au>,
	"Fastboot mailing list" <fastboot@lists.osdl.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Kexec with latest kernel fail
Date: Fri, 10 Nov 2006 01:18:37 -0800	[thread overview]
Message-ID: <86802c440611100118s39613504q335914f01273fd30@mail.gmail.com> (raw)
In-Reply-To: <2ea3fae10611092330q551127e0oad87775964fe7251@mail.gmail.com>

Andi,

On 11/9/06, yhlu <yinghailu@gmail.com> wrote:
> the /proc/iomem doesn't show RAM above 1M.
>
> I have increased linuxbios table at high 0xf0000-0xf0400 to
> 0xf0000-0x100000. the RAM above 1M show up.
>

Can you explain more about the patch?

I wonder what we suppose to do about [640K, 1M).
In LinuxBIOS we only set [0xa0000, 0xc0000) and [0xf0000, 0xf0400) to reserved,
[0xc0000, 0xf0000) and [0xf0400, 4G) as ram..

with your patch, the 1M above range will not show up on /proc/iomem

YH

[PATCH] Don't force reserve the 640k-1MB range
>From i386 x86-64 inherited code to force reserve the 640k-1MB area.
That was needed on some old systems.

But we generally trust the e820 map to be correct on 64bit systems
and mark all areas that are not memory correctly.

This patch will allow to use the real memory in there.

Or rather the only way to find out if it's still needed is to
try. So far I'm optimistic.

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=dbf9272e863bf4b17ee8e3c66c26682b2061d40d

  reply	other threads:[~2006-11-10  9:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10  1:41 Lu, Yinghai
2006-11-10  5:24 ` Eric W. Biederman
2006-11-10  7:30   ` yhlu
2006-11-10  9:18     ` Yinghai Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-10 20:01 Lu, Yinghai
2006-11-10  1:12 Lu, Yinghai
2006-11-10  1:27 ` Horms
2006-11-09  4:07 Lu, Yinghai
2006-11-09  5:48 ` [Fastboot] " Horms
2006-11-09  6:03   ` yhlu
2006-11-09  6:04   ` yhlu
2006-11-09  6:21     ` Horms
2006-11-09  7:36       ` Yinghai Lu
2006-11-10  0:47         ` Horms
2006-11-09 16:39 ` Don Zickus
2006-11-09 17:05   ` Yinghai Lu
2006-11-09 20:06   ` Jay Lan
2006-11-09 20:11     ` Vivek Goyal

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=86802c440611100118s39613504q335914f01273fd30@mail.gmail.com \
    --to=yinghai.lu@amd.com \
    --cc=ak@muc.de \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=horms@verge.net.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yinghailu@gmail.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
all inboxes | Powered by JetHome®