From: Mikael Pettersson <mikpe@csd.uu.se>
To: laughing@shared-source.org
Cc: esr@thyrsus.com, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.5-ac7
Date: Sun, 3 Jun 2001 14:04:16 +0200 (MET DST) [thread overview]
Message-ID: <200106031204.OAA29677@harpo.it.uu.se> (raw)
On Sun, 3 Jun 2001 00:23:10 +0100, Alan Cox wrote:
>2.4.5-ac6
>...
>o Resync with Eric's master Configure.help (Eric Raymond)
ac5->ac6 accidentally(?) dropped the help text for CONFIG_X86_UP_APIC.
Patch below (vs -ac7) adds it back. Please apply.
/Mikael
--- linux-2.4.5-ac7/Documentation/Configure.help.~1~ Sun Jun 3 12:59:52 2001
+++ linux-2.4.5-ac7/Documentation/Configure.help Sun Jun 3 13:06:50 2001
@@ -243,6 +243,18 @@
chip, if it's not found then Linux falls back to PC-style interrupt
handling.
+APIC Support on Uniprocessors
+CONFIG_X86_UP_APIC
+ APIC (Advanced Programmable Interrupt Controller) is a scheme for
+ delivering hardware interrupt requests to the CPU. It is commonly
+ used on systems with several CPUs. If you have a single-CPU system
+ which has a processor that has an integrated APIC, you can say Y
+ here to enable and use it. If you say Y here even though your
+ machine doesn't have an APIC, then the kernel will still run with no
+ slowdown at all. The advantage of APIC support is the possibility
+ to use performance counters, and the APIC based NMI watchdog which
+ detects hard lockups.
+
Kernel math emulation
CONFIG_MATH_EMULATION
Linux can emulate a math coprocessor (used for floating point
next reply other threads:[~2001-06-03 12:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-03 12:04 Mikael Pettersson [this message]
[not found] <mailman.991555081.25242.linux-kernel2news@redhat.com>
2001-06-03 20:51 ` Pete Zaitcev
2001-06-04 12:27 ` Pavel Machek
2001-06-05 15:03 ` Dominik Kubla
-- strict thread matches above, loose matches on Subject: below --
2001-06-03 15:49 Wayne.Brown
2001-06-04 20:10 ` Alan Cox
2001-06-02 23:23 Alan Cox
2001-06-03 7:46 ` Oleg Drokin
2001-06-03 11:19 ` Alan Cox
2001-06-03 12:33 ` Russell King
2001-06-03 14:02 ` Oleg Drokin
2001-06-03 14:45 ` Alan Cox
2001-06-03 14:51 ` Oleg Drokin
2001-06-03 14:54 ` Alan Cox
2001-06-04 1:49 ` lists
2001-06-03 13:59 ` Oleg Drokin
2001-06-04 17:56 ` Tom Rini
2001-06-04 17:59 ` Alan Cox
2001-06-04 18:49 ` Nicolas Pitre
2001-06-03 18:16 ` Philip Blundell
2001-06-03 20:50 ` Tom Rini
2001-06-04 12:37 ` Geert Uytterhoeven
2001-06-04 12:59 ` johan.adolfsson
2001-06-03 14:56 ` Nicolas Pitre
2001-06-03 15:03 ` Alan Cox
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=200106031204.OAA29677@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=esr@thyrsus.com \
--cc=laughing@shared-source.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®