Support remote operations in wineserver

Alexandre Julliard julliard at winehq.org
Thu Sep 23 13:38:53 CDT 2004


"Alexander Yaworsky" <yaworsky at migusoft.ru> writes:

> Ok, here is a draft working implementation of NtAllocateVirtualMemory.
> There are four mechanisms at all: signals, ptrace, service thread and wait. This
> implementation uses so-called wait approach: request is passed via wait_fd.
> The drawback is that request may not always be handled but most sane
> applications sooner or later fall into wait state. Also i'm going to try other
> mechanisms but their implementations seem will be very similar.

The main problem is that you can't make any assumption on the state of
the process, so you definitely cannot rely on it making a wait
call. Also you cannot do anything that requires taking a lock, so you
are basically limited to doing straight system calls in the remote
operation. That will probably require some restructuring of the
existing code, especially the memory management part.

-- 
Alexandre Julliard
julliard at winehq.org



More information about the wine-devel mailing list