linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: linux-kernel@vger.kernel.org, nemesis-lists@icequake.net
Subject: Re: APIC support on Slot-A Athlon, K6
Date: Mon, 8 Dec 2003 18:07:11 +0100 (MET)	[thread overview]
Message-ID: <200312081707.hB8H7B85014403@harpo.it.uu.se> (raw)

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)

             reply	other threads:[~2003-12-08 17:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 17:07 Mikael Pettersson [this message]
2003-12-09  5:03 ` APIC support on Slot-A Athlon, K6 [PATCH] Ryan Underwood
     [not found] <20031208102800.5409.87787.Mailman@lists.us.dell.com>
2003-12-08 11:58 ` APIC support on Slot-A Athlon, K6 Ryan Underwood
2003-12-08 12:06   ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2003-12-08 10:44 Mikael Pettersson
2003-12-08  8:48 Ryan Underwood

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=200312081707.hB8H7B85014403@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nemesis-lists@icequake.net \
    /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;
as well as URLs for NNTP newsgroup(s).