Hi Michael
have you thought about how this infrastructure would play well with
existing CPU hotplug code for ia64?
Once you return to user mode via the iret, is it possible that user mode
thread could get switched due to a pending cpu quiese attempt to remove
a cpu? (Current cpu removal code would bring the entire system to knees
by scheduling a high priority thread and looping with intr disabled, until the
target cpu is removed)
the cpu removal code would also attempt to migrate user process to another cpu,
retarget interrupts to another existing cpu etc. I havent tested the hotplug
code on sgi boxes so far. (only tested on some hp boxes by Alex Williamson
and on tiger4 boxes so far)
Cheers,
ashok
On Wed, Mar 23, 2005 at 08:38:33AM -0800, Michael Raymond wrote:
>
> Allow fast (1+us) user notification of device interrupts. This
> allows
> more powerful user I/O applications to be written. The process of
> porting
> to other architectures is straight forward and fully documented. More
> information can be found at [1]http://oss.sgi.com/projects/uli/.
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
