More seriously I've clean up the code and use thread local storage instead a big struct. The multiple image support is working and bootstraping too ;-)
Gwen On Fri, Jun 10, 2011 at 4:03 PM, Gwenael Casaccio <[email protected]> wrote: > On 06/09/2011 11:22 AM, Paolo Bonzini wrote: >> >> On 06/09/2011 11:05 AM, Gwenael Casaccio wrote: >>> >>> I think that's the right way but I want your opinion on the changes. >>> I plan to fix the multiple worlds support by : >>> - fix the world swapping crash :) >>> - see the impact on the vm (semaphore/events/...) >>> - introducing a model for the worlds >>> - the scheduling could be time shared for the worlds (Paolo what do >>> you think)? >> >> Why not parallel? M worlds == M threads, with inter-world >> synchronization primitives. Windows events look like a feasible model to >> use for synchronization primitives where you can wait for either any or >> all of N events to become signaled. Or Erlang-like channels too. >> >> How do you plan to move objects across worlds? >> >> Paolo > > *** BREAKING NEWS multi core image is working BREAKING NEWS *** > > Gwen > _______________________________________________ help-smalltalk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-smalltalk
