Re: [MiNT] Preemption in AES

[Jo Even Skarstein <joska@online.no>]

On Wed, 2013-03-06 at 21:15 +0100, Miro Kropáček wrote:


> Even higher, it's about receiving at least some CPU time for 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.

When I look at the code I see that my assumption was wrong. The
scheduler is called while performing these actions. So only screen
output should be blocked. I don't know why this isn't pre-empted - maybe
it's related to the VDI?

Jo Even