Angela Lin wrote: > On 1/30/07, Tim Ellison <[EMAIL PROTECTED]> wrote: >> Salikh Zakirov wrote: >>> * hythread_monitor_ functions provide native synchronization >>> primitives, which are not connected to java objects in any way, >>> and are not exposed to the VM, so these also can be >>> implemented directly in portlib as thin OS-function wrappers. >> >> But does the VM need to know when a thread has acquired an OS monitor? >> e.g. for monitoring/deadlock detection/debugging. >> <snip> > > Yes, you could bypass hythr in the portlib by using a lower-level API. > However, you will also bypass any VM instrumentation/debug tooling in > hythr. Customers would probably not like this approach. For example, I > think we've had complaints when our dump tooling didn't show details > of unattached threads in the VM process.
Agreed, we need to give the VM a chance to provide the thread functions directly so it can control the resources closely; and/or provide a working reference implementation of the required functions that the VM can augment. Tim
