From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@osdl.org>, Dave Olson <olson@unixfolk.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] Initial generic hypertransport interrupt support.
Date: Tue, 11 Jul 2006 08:39:22 +1000 [thread overview]
Message-ID: <1152571162.1576.122.camel@localhost.localdomain> (raw)
In-Reply-To: <m1bqrxm6zm.fsf@ebiederm.dsl.xmission.com>
On Mon, 2006-07-10 at 16:26 -0600, Eric W. Biederman wrote:
> This patch implements two functions ht_create_irq and ht_destroy_irq
> for use by drivers. Several other functions are implemented as helpers
> for arch specific irq_chip handlers.
>
> The driver for the card I tested this on isn't yet ready to be merged.
> However this code is and hypertransport irqs are in use in a few other
> places in the kernel. Not that any of this will get merged before
> 2.6.19
>
> Because the ipath-ht400 is slightly out of spec this code will need
> to be generalized to work there.
>
> I think all of the powerpc uses are for a plain interrupt controller
> in a chipset so support for native hypertransport devices is a little
> less interesting.
At this point, the only PPCs with HT interrupts that I know are 970
based solutions using the Apple U3/U4 bridges (and their IBM
counterparts). Thus all HT interrupts are routed to the MPIC as sources,
so things like masking, affinity, etc... are all handled at the MPIC
level, not at the HT level and they all originate from either an Apple
home made HT APIC or standard HT APICs in PCI-X/E tunnels. We still need
to poke around with the HT APICs for configuration and EOI on level
interrupts (due to a bug in the Apple MPIC, the EOI doesn't get sent
back to the HT APIC) but we have code locally in the MPIC driver to do
it and I don't think it would fit well a generic layer.
Things might be different in the future... but for now, I'm afraid I
have no use of that HT layer.
Cheers
Ben.
next prev parent reply other threads:[~2006-07-10 22:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 22:14 [PATCH 1/2] Add Hypertransport capability defines Eric W. Biederman
2006-07-10 22:26 ` [PATCH 2/2] Initial generic hypertransport interrupt support Eric W. Biederman
2006-07-10 22:39 ` Benjamin Herrenschmidt [this message]
2006-07-11 3:51 ` Eric W. Biederman
2006-07-11 5:20 ` Benjamin Herrenschmidt
2006-07-11 6:29 ` Eric W. Biederman
2006-07-11 7:29 ` Segher Boessenkool
2006-07-11 7:48 ` Eric W. Biederman
2006-07-11 9:15 ` Benjamin Herrenschmidt
2006-07-11 19:56 ` Eric W. Biederman
2006-07-11 22:18 ` Benjamin Herrenschmidt
2006-07-11 22:27 ` Andi Kleen
2006-07-12 3:05 ` Eric W. Biederman
2006-07-12 6:10 ` Dave Olson
2006-07-12 6:56 ` Eric W. Biederman
2006-07-13 3:56 ` Dave Olson
2006-07-13 15:13 ` Eric W. Biederman
2006-07-13 18:15 ` Dave Olson
2006-07-13 18:41 ` Eric W. Biederman
2006-07-13 19:00 ` Dave Olson
2006-07-13 19:20 ` Eric W. Biederman
2006-07-13 19:34 ` Dave Olson
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=1152571162.1576.122.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.com \
/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