From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: UP IO-APIC with ACPI table but no MP table?
Date: 02 Apr 2002 13:57:54 +0200 [thread overview]
Message-ID: <p731ydytirg.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <15529.39198.444056.901156@kim.it.uu.se.suse.lists.linux.kernel>
Mikael Pettersson <mikpe@csd.uu.se> writes:
> Is it possible to get the kernel to recognise and utilise the
> chipset's IO-APIC if the BIOS has no MP table but does list the
> IO-APIC in the ACPI table(s)?
The new Intel ACPI implementation now merged into 2.5 should support
this. Of course it may still not work on your particular BIOS.
> If it's possible, is it also meaningful to do this on UP?
Using the IO-APIC makes a lot of sense, because it is a much more
efficient interface to the interrupt controller.
-Andi
next parent reply other threads:[~2002-04-02 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15529.39198.444056.901156@kim.it.uu.se.suse.lists.linux.kernel>
2002-04-02 11:57 ` Andi Kleen [this message]
2002-04-02 11:42 UP IO-APIC with ACPI table but no MP table? Mikael Pettersson
2002-04-02 12:54 ` Arjan van de Ven
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=p731ydytirg.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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