[RFC/PATCH 0/16] Ops based MSI Implementation
David Miller
davem at davemloft.net
Mon Jan 29 10:51:55 EST 2007
From: ebiederm at xmission.com (Eric W. Biederman)
Date: Sun, 28 Jan 2007 16:38:28 -0700
> That isn't even the reason it is that way. It is because allocating
> 4096 irqs in a single vector is a bad idea, and because it requires you
> to pass type information of what kind of msi you are dealing with to the
> lower levels in an allocation routine that make it bad idea. Because
> if you don't consider the IBM HV it provides not benefit and just puts
> unnecessary loops, and type information in architecture code.
Eric, get over it, sparc64 will need this kind of abstraction
too in order to support MSI properly.
There are specific calls into the sparc64 hypervisor for MSI vs. MSI-X
configuration operations. So a type is necessary.
Sun Niagara and IBM RTAS hypervisors are not going to get
rearchitected because you peed your pants over this on some Linux
mailing list :-) Trust me on that one :))
More information about the Linuxppc-dev
mailing list