From: John Sigler <linux.kernel@free.fr>
To: linux-kernel@vger.kernel.org
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: BIOS implementors disabling the LAPIC
Date: Tue, 31 Jul 2007 10:06:54 +0200 [thread overview]
Message-ID: <46AEED9E.1050904@free.fr> (raw)
I have several systems here where Linux tells me:
Local APIC disabled by BIOS -- you can enable it with "lapic"
As far as I understand, the Local APIC was integrated directly to the
CPU 12-15 years ago. Why would a BIOS implementor choose to disable it?
(And what does it mean to "disable" the LAPIC?)
Note: the motherboard does not provide an IO-APIC.
I've ask the kernel to re-enable the LAPIC, and was able to use OProfile
in hardware counter mode, i.e. it seems to work fine.
Regards.
next reply other threads:[~2007-07-31 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 8:06 John Sigler [this message]
2007-07-31 10:27 ` BIOS implementors disabling the LAPIC Maciej W. Rozycki
2007-07-31 12:32 ` John Sigler
2007-07-31 12:55 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2007-07-31 12:53 Gregory Haskins
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=46AEED9E.1050904@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.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