mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ryan Underwood <nemesis-lists@icequake.net>
To: linux-kernel@vger.kernel.org
Subject: Re: APIC support on Slot-A Athlon, K6 [PATCH]
Date: Mon, 8 Dec 2003 23:03:08 -0600	[thread overview]
Message-ID: <20031209050308.GA10763@dbz.icequake.net> (raw)
In-Reply-To: <200312081707.hB8H7B85014403@harpo.it.uu.se>


[-- Attachment #1.1: Type: text/plain, Size: 1179 bytes --]

On Mon, Dec 08, 2003 at 06:07:11PM +0100, Mikael Pettersson wrote:
> On Mon, 8 Dec 2003 05:58:59 -0600, Ryan Underwood wrote:
> >> Furthermore, I/O-APIC usage requires (in hardware) that the
> >> processor has a local APIC.
> >
> >What can the APIC support alone accomplish, without an I/O-APIC?
> >Just NMI watchdog and related things? (looking at CONFIG_APIC help)
> >Looks like I/O-APIC is the real desired feature, but a functioning local
> >APIC, though not very useful by itself, is a prerequisite for it.
> 
> Local APIC gives you:
> - using the local APIC timer instead of the mobo's legacy timer
> - thermal management interrupts on P4s (dunno about K7s/K8s)
> - performance counter interrupts, which can be used as an NMI
>   source (watchdog, profiling) or for performance analysis
> 
> I/O-APIC gives you:
> - more interrupt vectors ==> less IRQ sharing ==> improved
>   stability and performance
> - lower-overhead interrupt management
> - I/O-APIC NMI watchdog (another timer with NMI delivery mode)

I attached a Kconfig patch more explicitly stating the prerequisites for
using the I/O-APIC.

-- 
Ryan Underwood, <nemesis@icequake.net>

[-- Attachment #1.2: kconfig.diff --]
[-- Type: text/plain, Size: 532 bytes --]

--- arch/i386/Kconfig.bak	2003-08-08 23:32:43.000000000 -0500
+++ arch/i386/Kconfig	2003-12-08 23:00:36.000000000 -0600
@@ -491,6 +491,10 @@
 	  If you have a system with several CPUs, you do not need to say Y
 	  here: the IO-APIC will be used automatically.
 
+	  A functioning local APIC is a prerequisite for using the I/O-APIC
+	  on uniprocessor machines. Sometimes working ACPI support is also
+	  required (depending on the BIOS implementation).
+
 config X86_LOCAL_APIC
 	bool
 	depends on !SMP && X86_UP_APIC

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-12-09  5:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 17:07 APIC support on Slot-A Athlon, K6 Mikael Pettersson
2003-12-09  5:03 ` Ryan Underwood [this message]

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=20031209050308.GA10763@dbz.icequake.net \
    --to=nemesis-lists@icequake.net \
    --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

Powered by JetHome