From: Paul Jackson <pj@sgi.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: mingo@elte.hu, bwalle@suse.de, hannes@saeurebad.de,
ying.huang@intel.com, linux-kernel@vger.kernel.org,
steiner@sgi.com
Subject: Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86_64
Date: Thu, 12 Jun 2008 15:10:32 -0500 [thread overview]
Message-ID: <20080612151032.5a59309b.pj@sgi.com> (raw)
In-Reply-To: <86802c440806121005g42f2e44cxbe5f7bdb06836a1e@mail.gmail.com>
Yinghai wrote:
> that function seems to increase the ebda to workaround some broken
> machine blindly.
Yes, true.
The reserve_ebda_region() has probably been like that for a while;
do you understand why it would be a problem conflicting with the
EFI memmap only now?
My other two concerns remain as well:
2) Is what amounts to a change from calling reserve_bootmem()
to calling reserve_early(), at the end of reserve_ebda_region()
in the 32 bit case (now that it is merged with the 64 bit code)
understood to be a desired and correct change?
3) There has been quite a few patches restructuring this early
memory reservation code over the last week. What is the
state of that work ... is it still "in progress" or is it
thought to be complete?
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.940.382.4214
next prev parent reply other threads:[~2008-06-12 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:06 Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86_64 Paul Jackson
2008-06-12 12:25 ` Yinghai Lu
2008-06-12 16:19 ` Paul Jackson
2008-06-12 17:05 ` Yinghai Lu
2008-06-12 20:10 ` Paul Jackson [this message]
2008-06-12 20:29 ` Yinghai Lu
2008-06-12 21:09 ` H. Peter Anvin
2008-06-12 21:52 ` Paul Jackson
2008-06-12 22:06 ` Yinghai Lu
2008-06-12 22:13 ` Paul Jackson
2008-06-12 22:39 ` H. Peter Anvin
2008-06-13 0:59 ` Huang, Ying
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=20080612151032.5a59309b.pj@sgi.com \
--to=pj@sgi.com \
--cc=bwalle@suse.de \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--cc=yhlu.kernel@gmail.com \
--cc=ying.huang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.