From: Jon Smirl <jonsmirl@gmail.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net,
Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
ian.pratt@cl.cam.ac.uk
Subject: Re: Interrupt forwarding
Date: Sun, 13 Mar 2005 10:56:08 -0500 [thread overview]
Message-ID: <9e473391050313075613352bba@mail.gmail.com> (raw)
In-Reply-To: <edb729416f39721ffa95b12180828c5d@cl.cam.ac.uk>
On Sun, 13 Mar 2005 10:01:42 +0000, Keir Fraser
<Keir.Fraser@cl.cam.ac.uk> wrote:
>
> On 12 Mar 2005, at 20:07, Jon Smirl wrote:
>
> > [jonsmirl@jonsmirl proc]$ cat interrupts
> > CPU0 CPU1
> > 0: 484259 448188 IO-APIC-edge timer
> > 8: 0 0 IO-APIC-edge rtc
> > 9: 0 0 IO-APIC-level acpi
> > 14: 776 762 IO-APIC-edge ide0
> > 15: 8040 7726 IO-APIC-edge ide1
> > 169: 37509 0 IO-APIC-level libata, uhci_hcd:usb4, eth0
> > 185: 5 0 IO-APIC-level ehci_hcd:usb1
> > 193: 548 272 IO-APIC-level uhci_hcd:usb2,
> > uhci_hcd:usb5
> > 201: 0 0 IO-APIC-level uhci_hcd:usb3
> > 209: 3 0 IO-APIC-level ohci1394
> > NMI: 0 0
> > LOC: 932357 932306
> > ERR: 0
> > MIS: 0
>
> Bizarre. Not only routed through an I/O APIC, but the IRQ numbers are
> large enough to probably be MSI vectors. Perhaps the mobo layout has
> legacy PCI slots sharing IRQ lines before reaching MSI logic in the
> chipset? Putting network on the same line as anything else is very
> sucky. Is this really a server-class board?
It is a Dell Poweredge 400SC server. I don't like how the net and
SATA drives are on the same IRQ.
I am running the latest linus bk kernel. The IRQ numbering system in
the kernel has been changed. The board is just a standard APIC without
MSI. No PCI Express.
Xen is planned for desktops too, right? Interrupts are shared all of
the time on desktop systems. It is not safe to assume you can get an
exclusive one.
>
> -- Keir
>
>
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-13 15:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 19:59 Interrupt forwarding Ian Pratt
2005-03-12 20:07 ` Jon Smirl
2005-03-13 10:01 ` Keir Fraser
2005-03-13 15:56 ` Jon Smirl [this message]
2005-03-13 16:01 ` Keir Fraser
2005-03-13 16:49 ` Jon Smirl
-- strict thread matches above, loose matches on Subject: below --
2005-03-12 18:11 Ian Pratt
2005-03-12 18:21 ` Keir Fraser
2005-03-12 18:33 ` Jon Smirl
2005-03-12 18:48 ` Keir Fraser
2005-03-12 18:53 ` Jon Smirl
2005-03-12 18:59 ` Jon Smirl
2005-03-12 18:02 Jon Smirl
2005-03-12 18:12 ` Mark Williamson
2005-03-14 15:39 ` Ronald G. Minnich
2005-03-14 15:44 ` Mark Williamson
2005-03-14 16:01 ` Ronald G. Minnich
2005-03-14 16:04 ` Ronald G. Minnich
2005-03-14 21:59 ` Andi Kleen
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=9e473391050313075613352bba@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.