On 10/08/08 13:56, Artem Kachitchkine wrote: > I missed this during case preparation: what is the requested release > binding?
This project seeks approval for a micro release binding. We are planning to integrate into Nevada and S10U8. > No support for x86? The project provides a generic DDI mechanism for drivers to create and manage requests for interrupts. And the project provides a generic NDI mechanism for the system to define interrupt pools, map requests into pools, and then balance together all the requests that were mapped to the same pool. If there is any mismatch, the framework adapts. That is, if a driver uses the new DDI interfaces but the system does not have any defined interrupt pools for the driver to use, then behavior reverts back to what currently exists. Likewise, if a driver is not using the new DDI interfaces but an interrupt pool is defined, the framework can again translate the driver's use of interrupts into the pool in such a way as to provide the previous type of behavior for that driver. We are providing a specific implementation for the PCIe nexus driver on SPARC to define interrupt pools so that drivers using the new DDI interfaces will get more interrupts through IRM when plugged into PCIe buses on SPARC based systems. But we are not providing a specific implementation to define interrupt pools on x86. There is a lot more work required to overhaul the interrupt handling on x86 first, and then the NDI interfaces can be used to define interrupt pools and plugin to IRM when that is done. -- Scott
