lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <46AEED9E.1050904@free.fr>
Date:	Tue, 31 Jul 2007 10:06:54 +0200
From:	John Sigler <linux.kernel@...e.fr>
To:	linux-kernel@...r.kernel.org
CC:	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: BIOS implementors disabling the LAPIC

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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ