From: Robert Hancock <hancockr@shaw.ca>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: IRQ splitting
Date: Thu, 05 Apr 2007 08:34:59 -0600 [thread overview]
Message-ID: <46150913.4000406@shaw.ca> (raw)
In-Reply-To: <fa.21iotKLTgoLpkKhrbSxrjy5v7hM@ifi.uio.no>
Jan Engelhardt wrote:
> Hello list,
>
>
>
> let's take the following /proc/interrupts dump (CPU2,CPU3 trimmed)...
>
> CPU0 CPU1
> 0: 37041766 37038991 IO-APIC-edge timer
> 1: 10 2 IO-APIC-edge i8042
> 8: 0 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-level acpi
> 12: 114 0 IO-APIC-edge i8042
> 14: 25219 5800049 IO-APIC-edge ide0
> 201: 260381 238454 IO-APIC-level aacraid
> 209: 0 0 IO-APIC-level ohci_hcd:usb1
> 217: 0 0 IO-APIC-level ehci_hcd:usb2
> 225: 57531742 0 IO-APIC-level eth0,radeon@pci:0000:03:00.0
> 233: 26 0 IO-APIC-level eth1
> NMI: 1661 1397
> LOC: 147579966 147579949
> ERR: 0
> MIS: 0
>
> My question is whether it is possible that eth0's interrupts go to CPU0
> and radeon's to CPU1, and if so, how I would enable that. Alternatively,
> is it possible to just move eth0 or radeon to a different interrupt?
Generally (at least in APIC mode) the IRQ assignments are based on
hard-wired interrupt lines on the board. In this case, the slots that
the Radeon and eth0 card are in likely share a physical interrupt line
and there is no way to separate them in software. You can try moving the
card(s) to different slots..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-05 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.21iotKLTgoLpkKhrbSxrjy5v7hM@ifi.uio.no>
2007-04-05 14:34 ` Robert Hancock [this message]
2007-04-05 19:23 ` IRQ splitting Stephen Hemminger
2007-04-05 20:37 ` Jan Engelhardt
2007-04-05 19:45 ` Stephen Hemminger
2007-04-05 10:40 Jan Engelhardt
2007-04-05 12:13 ` Jiri Kosina
2007-04-05 13:11 ` Mark Hounschell
2007-04-05 14:14 ` Lennart Sorensen
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=46150913.4000406@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jengelh@linux01.gwdg.de \
--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