From: Matthew Wilcox <matthew@wil.cx>
To: Mark Maule <maule@sgi.com>
Cc: Greg KH <gregkh@suse.de>,
linuxppc64-dev@ozlabs.org, linux-pci@atrey.karlin.mff.cuni.cz,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Tony Luck <tony.luck@intel.com>
Subject: Re: [PATCH 0/3] msi abstractions and support for altix
Date: Thu, 22 Dec 2005 13:50:23 -0700 [thread overview]
Message-ID: <20051222205023.GK2361@parisc-linux.org> (raw)
In-Reply-To: <20051222203824.GJ17552@sgi.com>
On Thu, Dec 22, 2005 at 02:38:24PM -0600, Mark Maule wrote:
> Because on ia64 IA64_FIRST_DEVICE_VECTOR and IA64_LAST_DEVICE_VECTOR
> (from which MSI FIRST_DEVICE_VECTOR/LAST_DEVICE_VECTOR are derived) are not
> constants. The are now global variables (see change to asm-ia64/hw_irq.h)
> to allow the platform to override them. Altix uses a reduced range of
> vectors for devices, and this change was necessary to make assign_irq_vector()
> to work on altix.
To be honest, I think this is just adding a third layer of paper over
the crack in the wall. The original code assumed x86; the ia64 port
added enough emulation to make it look like x86 and now altix fixes a
couple of assumptions. I say: bleh.
What we actually need is an interface provided by the architecture that
allocates a new irq. I have a hankering to implement MSI on PA-RISC but
haven't found the time ...
next prev parent reply other threads:[~2005-12-22 20:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 20:15 [PATCH 0/3] msi abstractions and support for altix Mark Maule
2005-12-22 20:15 ` [PATCH 1/3] msi vector targeting abstractions Mark Maule
2006-01-03 22:39 ` Grant Grundler
2006-01-03 23:50 ` Mark Maule
2006-01-04 0:20 ` Grant Grundler
2006-01-04 0:27 ` Greg KH
2006-01-04 3:52 ` Mark Maule
2005-12-22 20:15 ` [PATCH 2/3] per-platform IA64_{FIRST,LAST}_DEVICE_VECTOR definitions Mark Maule
2006-01-04 0:01 ` Grant Grundler
2005-12-22 20:16 ` [PATCH 2/3] altix: msi support Mark Maule
2005-12-22 20:22 ` [PATCH 0/3] msi abstractions and support for altix Greg KH
2005-12-22 20:26 ` Mark Maule
2005-12-22 20:34 ` Greg KH
2005-12-22 20:38 ` Mark Maule
2005-12-22 20:50 ` Matthew Wilcox [this message]
2006-01-03 3:22 ` Mark Maule
2006-01-03 6:07 ` Greg KH
2006-01-10 17:00 ` Mark Maule
2006-01-10 17:03 ` Christoph Hellwig
2006-01-10 17:11 ` Greg KH
2005-12-22 21:44 ` Greg KH
2005-12-23 15:32 ` Mark Maule
2005-12-23 16:32 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2006-03-29 2:31 Mark Maule
2006-03-21 14:34 Mark Maule
2006-03-21 21:53 ` David S. Miller
2006-01-19 19:46 Mark Maule
2006-01-11 22:16 Mark Maule
2006-01-11 15:52 Mark Maule
2005-12-22 17:15 Mark Maule
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=20051222205023.GK2361@parisc-linux.org \
--to=matthew@wil.cx \
--cc=gregkh@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc64-dev@ozlabs.org \
--cc=maule@sgi.com \
--cc=tony.luck@intel.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