From: Helge Hafting <helgehaf@aitel.hist.no>
To: DervishD <raul@pleyades.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SMP or UP???
Date: Mon, 12 Jan 2004 14:35:18 +0100 [thread overview]
Message-ID: <4002A296.4010305@aitel.hist.no> (raw)
In-Reply-To: <20040112122538.GD18408@DervishD>
DervishD wrote:
> Hi Mikael :)
>
> * Mikael Pettersson <mikpe@csd.uu.se> dixit:
>
>>>kernel: found SMP MP-table at 000fb210
>>> What, SMP table?
>>
>>You have an anti-problem. The chipset includes an I/O-APIC
>>(good) and your mobo manufacturer was decent enough to include
>>the appropriate BIOS MP tables to describe it to the OS.
>
>
> Oh, nice. I thought that the mobo was a simple reisuing of a SMP
> mobo from Gigabyte with one socket removed O:)
>
>
>>Other manufacturers skip the MP table, forcing you to enable
>>ACPI and pray it actually works.
>
>
> Excuse my ignorance but: why a UP system needs the MP table? Why
> the I/O-APIC needs anything related with multiprocessor in an UP
> system?. I lost my way on hardware back in the 486, I think...
>
The MP table tells the kernel details about that I/O-APIC.
(Advanced Programmable Interrupt Controller).
This isn't really about SMP, but every SMP board has
one or more APICs. They have to. It is optional
on a uniprocessor board, but it is nice to have as it
gives lower interrupt latency.
Helge Hafting
next prev parent reply other threads:[~2004-01-12 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 12:11 SMP or UP??? Mikael Pettersson
2004-01-12 12:25 ` DervishD
2004-01-12 13:35 ` Helge Hafting [this message]
2004-01-12 16:21 ` DervishD
-- strict thread matches above, loose matches on Subject: below --
2004-01-12 10:20 DervishD
2004-01-12 15:30 ` Matthew D. Pitts
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=4002A296.4010305@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=raul@pleyades.net \
/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