UltraSPARC I, II and III have them as well.
We were thinking about adding such a support by extending the ptrace system
call. In any case it seems to me like your interface is too much
architecture specific (haven't studied your patch deeply), the interface
should have some architecture neutral control, like you'd say you're
interested in that and that and it would tell you either ok, this machine
supports it, or no, sorry, this architecture cannot do it, and there are some
performance issues in your patch, like the switch_to function should be put
into some arch specific header and inlined into schedule, as that routine must
fly... Also, we should answer the question to whom do irqs belong to, is it
the current process or to nobody, or to any other task? That won't show in
user time, of course, but in task kernel time for sure.
Jakub Jelinek | firstname.lastname@example.org | http://sunsite.mff.cuni.cz
Administrator of SunSITE Czech Republic, MFF, Charles University
Ultralinux - first 64bit OS to take full power of the UltraSparc
Linux version 2.1.65 on a sparc64 machine (333.41 BogoMips).