Thread suspension happens in many situations in JVM, such as for GC,
for java.lang.Thread.suspend(), etc. There are various techniques to
suspend a thread. Basically we can classify them into two categories:
preemptive and voluntary.
The preemptive approach requires the suspender, say a GC
Some time ago someone on this list pointed to a paper from Sun folks
about this subject.
From what I remember, they tried the folllowing tecniques:
-Pooling on back-edges and call/return, using ether a boolean flag or
forcing a page-fault at a specific address. They noticed that
page-faulting
From: Xiao-Feng Li [EMAIL PROTECTED]
Thread suspension happens in many situations in JVM, such as for GC,
for java.lang.Thread.suspend(), etc. There are various techniques to
suspend a thread. Basically we can classify them into two categories:
preemptive and voluntary.
The preemptive
Hi Mladen,
I am curious about 'light-weight' native calls for primitive array
type you mentioned below. In the general case, a GC might move the
primitive array while the native method is operating on the array.
Can you tell us how the light-weight interface would deal with this
situation?
I would like to invite discussion and comments from the community on the
VM Accessor component in the Harmony Modular JVM diagram, on its
functionality, design and implementation. Here are some initial
thoughts.
These are a helper set of singleton Java classes to support Classlibrary
Hi list,
I've been following the discussion about the VM/Classlibrary interface and
VMAccessors and I am a little confused why to separate VMAccessors from
VM/Classlibrary interface. I learned from the HarmonyArchitecture Wiki that
VMAccessors provide efficient accessing to VM classes, methods
