RFR: JDK-8212186: JVMTI lacks a few GC barriers/hooks

Aleksey Shipilev shade at redhat.com
Thu Oct 18 08:32:32 UTC 2018

On 10/18/2018 10:13 AM, Per Liden wrote:
> On 10/18/2018 09:46 AM, Aleksey Shipilev wrote:
>> Shenandoah does tracing for external heap walks, on the off chance external walk is requested
>> mid-marking. There are other ways to do this, e.g. wait for marking to complete before doing
>> external walk, which gets us back to heap parsability :)
> We initially did that in ZGC, but found that forcing the GC to be in a specific state before you can
> do certain operations just wasn't very attractive (more complex code, potentially stalled
> operations, strange error paths, etc). So, I think you made the right choice ;)

Roman would be happy to hear that. *I* was insisting to drop the additional tracing code and just
wait for marking to be over. :)


More information about the hotspot-runtime-dev mailing list