Kernel/user mode threads, semaphores, mutexes, msg queue, even

Kernel/user mode threads, semaphores, mutexes, msg queue, even

Post by TmluYSBQaG » Wed, 20 Aug 2008 06:30:00


I've done some more reading, please confirm my thoughts below:

First of all, I need to have the IST in kernel-mode driver to change the
usermode thread priority if it can. But if the thread handle can't be pass
via ioctl, I can use DuplicateHandle to solve the problem.

Secondly, in the case of events, mutexes, semaphores, or msg queues, I can
use the names which can be defined in the header files, or use
DuplicateHandle.

Thanks for your help.

Nina
 
 
 

Kernel/user mode threads, semaphores, mutexes, msg queue, even

Post by Paul G. To » Wed, 20 Aug 2008 06:38:21


Why? There's no reason to be changing the priority of user-mode threads
from a driver that I can think of.


Again, it would help if you'd finish your thought. "I can use x, y, z."
FOR WHAT? Yes, if the user mode program needs to pass an event to your
driver which the driver will set when something is ready or some event has
occurred that the user mode program has asked for notifications about, you
could use a named event on both ends or use DuplicateHandle() in the driver
to get a handle that points to the same object as the user mode handle
passed in some IOCTL.

Paul T.