Class loader is started from kernel and locks up everything (namely -
snaps) while is working.
One possible solution is to replace VM command 'summon class' with direct
access to userland class loader - but then what we have to do if kernel
itself will need some class?
Other possible hack is:
- after 'summon class' is called and class is not found in fast kernel hash
(which we need to implement as well) user code IP is stepped back to the
beginning of 'summon class' instruction and thread is put asleep. After the
finish of userland class loader thread is awaken and restarts its class
request, wchich is finished quickly this time, because requested class is
already in the fast kernel hash (which...;).
Original issue reported on code.google.com by dmitry.zavalishin@gmail.com on 5 Sep 2009 at 10:34
Original issue reported on code.google.com by
dmitry.zavalishin@gmail.com
on 5 Sep 2009 at 10:34