From: Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Interrupt redirection problem
Date: Wed, 27 Jun 2001 08:22:27 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005781@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590693005755@msgid-missing>
Andreas Schwab wrote:
>
> As you can see, cpu0 is processing the majority of interrupts (91%,
> ignoring the SAPIC interrupts). Why?
This is not the case on my system. On the contrary, CPU3 seems to receive
the vast majority of interrupts. (I have "Force IRQ redirection" enabled).
52: 139 1 671 167542 IO-SAPIC-level e100
54: 0 0 0 0 IO-SAPIC-level usb-uhci
57: 0 0 5 8072 IO-SAPIC-level Mylex eXtremeRAID 2000
61: 21 1 1856 66170 IO-SAPIC-level qla1280
63: 0 0 178 3896 IO-SAPIC-level aic7xxx
Martin
--
Martin Wilck <Martin.Wilck@fujitsu-siemens.com>
FSC EP PS DS1, Paderborn Tel. +49 5251 8 15113
next prev parent reply other threads:[~2001-06-27 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-25 15:35 [Linux-ia64] Interrupt redirection problem Andreas Schwab
2001-06-27 8:22 ` Martin Wilck [this message]
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-105590693005781@msgid-missing \
--to=martin.wilck@fujitsu-siemens.com \
--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