Re: [PATCH v2 0/2] MR7169: ntdll: Fix the return value of NtDelayExecution.

[Paul Gofman (＠gofman)]

Paul Gofman (@gofman) commented about dlls/ntdll/tests/sync.c:
> -
>            break;
> -
>        }
> -
>    }
> - }
> -
> - todo_wine ok( total_noyields[0] > 0, "Expected > 0 STATUS_NO_YIELD_PERFORMED results for non-alertable zero-timeout delays.\n" );
> - todo_wine ok( total_noyields[1] > 0, "Expected > 0 STATUS_NO_YIELD_PERFORMED results for alertable zero-timeout delays.\n" );
> -
> - param.ready = CreateEventA( NULL, FALSE, FALSE, NULL );
> - ok( param.ready != NULL, "CreateEvent failed, error %lu\n", GetLastError() );
> - param.completion = CreateEventA( NULL, FALSE, FALSE, NULL );
> - ok( param.completion != NULL, "CreateEvent failed, error %lu\n", GetLastError() );
> - param.non_zero_timeout = FALSE;
> -
> - param_timeout = param;
> - param_timeout.ready = CreateEventA( NULL, FALSE, FALSE, NULL );

Maybe I am missing something, but why do you need those additional threads, is there any cross-thread specific here? You could maybe just queue APCs to the same thread and check satisfied and timed out waits also on the same thread setting the desired event state upfront?