Changeset 13102

Timestamp:

Oct 27, 2009, 4:08:15 AM (15 years ago)

Author:

Gary Byers

Message:

In the windows version of raise_thread_interrupt(), don't try to
use either CancelIoEx (if it exists ...) or CancelIo() to cancel
pending I/O operations. (This probably means that we can drop
the stuff that maintains tcr->pending_io.) CancelIo() only cancels
requests made by the calling thread (useful ...), and CancelIoEx()
seems to require that the thread doing the indicated I/O operation
is runnable (not suspended); we don't have a good idea of what I/O
operations are pending unless the thread's suspended. What a steaming
pile of crap Windows is ...

File:

• trunk/source/lisp-kernel/thread_manager.c (modified) (2 diffs)

trunk/source/lisp-kernel/thread_manager.c

@@ -106 +106 @@
        !((where < (pc) (ts->high)) &&
          (where >= (pc) (ts->low))))) {
+
+    target->interrupt_pending = (1LL << (nbits_in_word - 1LL));
+
+#if 0
     /* If the thread's in a blocking syscall, it'd be nice to
        get it out of that state here. */
     GetThreadIOPendingFlag(hthread,&io_pending);
-    target->interrupt_pending = (1LL << (nbits_in_word - 1LL));
     if (io_pending) {
       pending_io * pending = (pending_io *) (target->pending_io_info);
@@ -120 +123 @@
       }
     }
+#endif
     if (pCancelSynchronousIo) {
       pCancelSynchronousIo(hthread);