From: Segher Boessenkool <segher@kernel.crashing.org>
To: ebiederm@xmission.com (Eric W. Biederman)
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
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 09:29:29 +0200 [thread overview]
Message-ID: <9ABD3384-5829-4365-988C-43310D374CE5@kernel.crashing.org> (raw)
In-Reply-To: <m1veq4iri1.fsf@ebiederm.dsl.xmission.com>
> As for supporting multiple irqs in plain MSI mode, I don't think
> we want to do that. The problem is that multiple interrupts
> in msi mode cannot be individually routed.
On some(/many/most) platforms that isn't a problem. Platforms
for which it is can just refuse to allocate more than one MSI
at once.
> I think we really want
> to encourage vendors who are building cards with multiple MSI irqs
> to use MSI-X. MSI-X has a lot fewer ugly special cases and all
> architectures can individually route the irqs.
We still should support whatever hardware already exists, if
possible.
> If there are interesting cards that support just MSI mode and really
> need more than one irq I would be happy to reconsider that decision
> but my impression was that plain MSI was basically not quite flexible
> enough to really be interesting, and supporting just one MSI irq was
> ok but any more would lead to all kinds of strange special cases.
Individual drivers can deal with those special cases if they are device-
specific; and the platform can just refuse to do more than one MSI if
something platform-specific would prevent correct operation.
It would be nice to have the MSI and MSI-X interfaces have the same
calling convention; in fact, they can probably be folded into one.
Segher
next prev parent reply other threads:[~2006-07-11 7:29 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
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 [this message]
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=9ABD3384-5829-4365-988C-43310D374CE5@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.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
all inboxes | Powered by JetHome®