public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Interrupt redirection problem
Date: Mon, 25 Jun 2001 15:35:07 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590693005755@msgid-missing> (raw)

This is the output of /proc/interrupts on a Lion that has been up for 9 days:

           CPU0       CPU1       CPU2       CPU3       
 32:       2226         19          0          0   IO-SAPIC-edge  keyboard
 33:          2          2          0          0   IO-SAPIC-edge  ide1
 34:          4          2          0          0   IO-SAPIC-edge  ide0
 36:          0          0          0          0   IO-SAPIC-edge  PS/2 Mouse
 44:       1180        131          2         47   IO-SAPIC-edge  serial
 48:   22811357    1510005      31585     155591  IO-SAPIC-level  eth0
 54:          0          0          0          0  IO-SAPIC-level  usb-uhci
 61:    4485678     808931      11218      97495  IO-SAPIC-level  qla1280
238:          0          0          0          0           SAPIC  perfmon
239:  796793291  796794391  796795076  796794435           SAPIC  timer
254:    8256864   11570234   11685908   11611853           SAPIC  IPI
NMI:          0          0          0          0 
ERR:          0

As you can see, cpu0 is processing the majority of interrupts (91%,
ignoring the SAPIC interrupts).  Why?

Andreas.

-- 
Andreas Schwab                                  "And now for something
SuSE Labs                                        completely different."
Andreas.Schwab@suse.de
SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5


             reply	other threads:[~2001-06-25 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-25 15:35 Andreas Schwab [this message]
2001-06-27  8:22 ` [Linux-ia64] Interrupt redirection problem Martin Wilck
2001-06-27 15:50 ` Miller, Mike (OS Dev)

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=marc-linux-ia64-105590693005755@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@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