[jdk17u-dev] RFR: 8325587: Shenandoah: ShenandoahLock should allow blocking in VM [v2]

[duke]

On Mon, 19 Aug 2024 15:29:29 GMT, Xiaolong Peng <xpeng at openjdk.org> wrote:

>> Hi, 
>>     This PR is a Backport of [JDK-8325587](https://bugs.openjdk.org/browse/JDK-8325587): Shenandoah: ShenandoahLock should allow blocking in VM, the original commit was authored by Aleksey Shipilev on 21 Feb 2024 and was reviewed by Robbin Ehn and Roman Kennke, and already backported to jdk21.
>>      It is not a clean backport for JDK17 due to code style change(NULL -> nullptr) and thread header file and API changes.   
>>     This is the first backport of a series of improvements for ShenandoahLock to improve contention issue which we I have seem in our customer's production load running with JDK17, here are the series of improvements I'm going to backport to JDK17:
>> 
>> | Bug         | Title                                          |
>> | ----------- | ---------------------------------------------- |
>> | [JDK-8325587](https://bugs.openjdk.org/browse/JDK-8325587) | ShenandoahLock should allow blocking in VM     |
>> | [JDK-8331405](https://bugs.openjdk.org/browse/JDK-8331405) | Optimize ShenandoahLock with TTAS              |
>> | [JDK-8331411](https://bugs.openjdk.org/browse/JDK-8331411) | Reconsider spinning duration in ShenandoahLock |
>> | [JDK-8335904](https://bugs.openjdk.org/browse/JDK-8335904) | Fix invalid comment in ShenandoahLock          |
>> 
>> 
>> Best,
>> Xiaolong. 
>> 
>> 
>> Additional tests:
>> - [x] hotspot_gc_shenandoah
>> - [x] Linux x86_64 server fastdebug, all passes with -XX:+UseShenandoahGC
>
> Xiaolong Peng has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Use thread->as_Java_thread() instead of static_cast

@pengxiaolong 
Your change (at version 22086ff28b9a797c3841a854b43dbaece8908530) is now ready to be sponsored by a Committer.

-------------

PR Comment: https://git.openjdk.org/jdk17u-dev/pull/2797#issuecomment-2325606143