Ole, 06.03.2013 21:28:31:
Am Mittwoch, den 06.03.2013, 21:15 +0100 schrieb Miro Kropáček <miro.kropacek@gmail.com>:the application :) As pointed out on another forum, it's probably because of the fact that XaAES, as a kernel module, runs in supervisor and therefore is not preempted until finished with the VDI/AES/whatever task.
AFAIK XaAES switches to user-mode and the trap-code runs on behalf of the client not the kernel. How should multiple evnt_multi-calls work if they would not allow preemption?
-- Helmut Karlowski