At Tue, 5 Apr 2016 08:42:28 -0400, Philippe Meunier wrote: > Matthew Flatt wrote: > >Since, as you note, units of JIT > >generation tend to be smaller than a page, this creates trouble if > >JITted code running in one thread is allocated on the same page as > >JITting in progress in another thread. > > My guess is that from the point of view of security the proper way to > solve this would be either to synchronize access to the page between > the two threads and flip the writable/executable permissions depending > on which thread is currently locking the page
Ok, I suppose nothing in my message suggests that I had considered the possibility of protecting a contended resource with a lock... So, just for the record, that looks hard to me --- not just to make perform well but to implement all with our current combination of JIT, libffi, futures, and places. But if someone has specific ideas that are connected to the current implementation, that would be great. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
