Thread (102 messages) 102 messages, 10 authors, 2007-02-01

Re: [RFC/PATCH 0/16] Ops based MSI Implementation

From: Michael Ellerman <hidden>
Date: 2007-01-26 01:05:07

On Thu, 2007-01-25 at 13:55 -0800, David Miller wrote:
From: Greg KH <redacted>
Date: Thu, 25 Jan 2007 13:53:07 -0800
quoted
On Thu, Jan 25, 2007 at 07:34:07PM +1100, Michael Ellerman wrote:
quoted
OK, here's a first cut at moving ops based MSI into the generic code. I'm
posting this now to make sure I'm not heading off into the weeds.

The fifth patch contain the guts of it, I've included the MPIC and
RTAS backends as examples. In fact they actually work.

In order to smoothly merge this with the old MSI code, the two will need to
coexist in the tree for at least a few commits, so I've added (invisible)
Kconfig symbols to allow that.

I plan to merge the Intel code by:
 * copying it into drivers/pci/msi/intel.c with zero changes.
 * providing a minimal shim to connect the ops code to the intel code.
 * at this point the code should be functional but ugly as hell.
 * via a longish series of patches, adapt the intel code to better match
   the new ops code.
 * this should allow us to bisect through to find any mistakes.

If people think that's crazy and or stupid please let me know :)
At first glance, this looks sane.  I'll apply the first 4 patches to my
trees, and hold off on the rest until you have the intel patches
finished.
I'll also look into a sparc64 implementation as soon as I find the
time.
That'd be great. The more backends we have the more likely we are to
find the bugs and bogosities in my design.

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help