Hi, I noticed that in gnumach/i386/i386/iopb.c, i386_io_port_add is careful to release all locks while running kalloc() to allocate some memory for the I/O bitmap, and goes back to retry via goto.
Is this in general a good strategy? What is the danger that purposedly is avoided here? Do I need to do a similar thing when locking the task I/O bitmap in the new code? Thanks, Marcus _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-hurd