From: "Huang, Ying" <ying.huang@intel.com>
To: Paul Jackson <pj@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, "H. Peter Anvin" <hpa@zytor.com>,
andi@firstfloor.org, mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH] x86 boot: Pass E820 memory map entries more than 128 via linked list of setup data
Date: Mon, 23 Jun 2008 13:54:01 +0800 [thread overview]
Message-ID: <1214200441.25753.5.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <20080618114511.GB28838@elte.hu>
Hi, Paul,
This patch can be used for machine whose E820 memory map has more than
128 entries. So it is not necessary to use EFI memory map for this (EFI
memory map is used for EFI runtime services only).
With this patch, your previous patch:
x86 boot: add code to add BIOS provided EFI memory entries to kernel
is not necessary, so can be reversed.
What do you think about that?
Best Regards,
Huang Ying
On Wed, 2008-06-18 at 13:45 +0200, Ingo Molnar wrote:
> * Huang, Ying <ying.huang@intel.com> wrote:
>
> > Because of the size limits of struct boot_params (zero page), the
> > maximum number of E820 memory map entries can be passed to kernel is
> > 128. As pointed by Paul Jackson, there is some machine produced by SGI
> > with so many nodes that the number of E820 memory map entries is more
> > than 128. To enabling Linux kernel on these system, a new setup data
> > type named SETUP_E820_EXT is defined to pass additional memory map
> > entries to Linux kernel.
> >
> > This patch is based on x86/auto-latest branch of git-x86 tree and has
> > been tested on x86_64 and i386 platform.
>
> applied to tip/x86/mpparse, thanks.
>
> this bit collided with a recent change:
>
> > - do {
> > - u64 start = biosmap->addr;
> > - u64 size = biosmap->size;
> > - u64 end = start + size;
> > - u32 type = biosmap->type;
> > -
> > - /* Overflow in 64 bits? Ignore the memory map. */
> > - if (start > end)
> > - return -1;
> > -
> > - add_memory_region(start, size, type);
> > - } while (biosmap++, --nr_map);
> > - return 0;
> > + return __copy_e820_map(biosmap, nr_map);
>
> because add_memory_region() got renamed to e820_add_region(). I did the
> obvious fixup.
>
> Ingo
next prev parent reply other threads:[~2008-06-23 5:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-11 3:33 [PATCH] x86 boot: Pass E820 memory map entries more than 128 via linked list of setup data Huang, Ying
2008-06-18 11:45 ` Ingo Molnar
2008-06-23 5:54 ` Huang, Ying [this message]
2008-06-23 6:53 ` Paul Jackson
2008-06-23 7:21 ` Huang, Ying
2008-06-23 8:47 ` Paul Jackson
2008-06-23 9:14 ` Huang, Ying
2008-06-23 9:48 ` Paul Jackson
2008-06-24 1:09 ` Huang, Ying
2008-06-24 5:45 ` H. Peter Anvin
2008-06-24 7:03 ` 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=1214200441.25753.5.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=pj@sgi.com \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@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