linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yhlu <yhlu.kernel@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andi Kleen <ak@muc.de>, Vivek Goyal <vgoyal@in.ibm.com>,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Morton Andrew Morton <akpm@osdl.org>
Subject: Re: Inclusion of x86_64 memorize ioapic at bootup patch
Date: Sat, 7 Jan 2006 11:36:31 -0800	[thread overview]
Message-ID: <86802c440601071136n14a0851we97f6db04f940d68@mail.gmail.com> (raw)
In-Reply-To: <m1ek3k2ojo.fsf@ebiederm.dsl.xmission.com>

MPTABLE in LinuxBIOS is put from 0x20, if the system has too many cpu
and devices (slots)  the mptable will get bigger than 0x464, so it
will use 0x40:67....

We need to put mptable to [0xf0000:0x100000] together with acpi tables.

and if it is bigger than 64k, then we have to put it on special
postion ...from 1K, and pass the posstion of mptable to the kernel via
command line.

I will update the code in LinuxBIOS.

Thanks

YH

  reply	other threads:[~2006-01-07 19:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07  1:32 Inclusion of x86_64 memorize ioapic at bootup patch Lu, Yinghai
2006-01-07  2:32 ` yhlu
2006-01-07  6:38   ` yhlu
2006-01-07  7:20     ` yhlu
2006-01-07  9:43       ` yhlu
2006-01-07 12:46         ` Eric W. Biederman
2006-01-07 19:36           ` yhlu [this message]
2006-01-07 19:44             ` Eric W. Biederman
2006-01-07 21:35               ` yhlu
  -- strict thread matches above, loose matches on Subject: below --
2006-01-07  0:35 Lu, Yinghai
2006-01-07  1:14 ` Eric W. Biederman
2006-01-03  4:46 Vivek Goyal
2006-01-06  0:30 ` Yinghai Lu
2006-01-06  0:38   ` Andrew Morton
2006-01-06  4:50     ` Vivek Goyal
2006-01-06  8:02     ` Eric W. Biederman
2006-01-06 18:59       ` Andi Kleen
2006-01-06  8:24   ` Eric W. Biederman
2006-01-06 23:48 ` Andi Kleen
2006-01-07  0:00   ` Yinghai Lu
2006-01-07  0:29     ` Eric W. Biederman

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=86802c440601071136n14a0851we97f6db04f940d68@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@in.ibm.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;
as well as URLs for NNTP newsgroup(s).