From: Yinghai <yinghai@kernel.org>
To: sreenivasa reddy berahalli <sreenivasa-reddy-berahalli@hp.com>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
Feng Tang <feng.tang@linux.intel.com>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: MPS table vs ACPI
Date: Wed, 29 Jun 2011 17:40:37 -0700 [thread overview]
Message-ID: <C8998C1F-0C0B-4B82-841A-16FD6829A90C@kernel.org> (raw)
In-Reply-To: <4E0BA7FE.9050607@hp.com>
On Jun 29, 2011, at 3:32 PM, sreenivasa reddy berahalli <sreenivasa-reddy-berahalli@hp.com> wrote:
> Hello All,
>
> Recent interaction with BIOS teams within in my Organization left me
> wondering if MP table spec from Intel is no more a mandatory one
> http://www.intel.com/design/pentium/datashts/24201606.pdf
>
> Section #8.4.5 http://www.intel.com/Assets/PDF/manual/253668.pdf
> Talks as ACPI or MPS table.
> That means BIOS can report through ACPI tables only.
>
> I looked through x86 boot sequence and notice Linux scanning for MPS
> table in below locations and Linux doesn't seem to go further without
> MPS table or doesn't know how to live with ACPI only.
> 1) Scan the bottom 1K for a signature
> 2) Scan the top 1K of base RAM
> 3) Scan the 64K of bios
Have one system with x2apic pre-enabled in bios, and it does not have mps table from bios. At least 2.6.32 based distribution kernel works well.
Current kernel works well too if you have acpi enabled in kernel.
Mptable assume apicid is 8 bits
Thanks
Yinghai
prev parent reply other threads:[~2011-06-30 0:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 22:32 sreenivasa reddy berahalli
2011-06-30 0:40 ` Yinghai [this message]
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=C8998C1F-0C0B-4B82-841A-16FD6829A90C@kernel.org \
--to=yinghai@kernel.org \
--cc=ebiederm@xmission.com \
--cc=feng.tang@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sreenivasa-reddy-berahalli@hp.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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®