RFR (S) 8038939: Some options related to RTM locking optimization works inconsistently
Vladimir Kozlov
vladimir.kozlov at oracle.com
Tue Apr 8 21:39:54 UTC 2014
http://cr.openjdk.java.net/~kvn/8038939/webrev
https://bugs.openjdk.java.net/browse/JDK-8038939
Switch UseRTMXendForLockBusy flag ON by default and change code to
address issues described in the bug report.
Jump to inflated locking when inflated lock is detected without starting
a new transaction regardless to RTMXendForLockBusy value.
Now it retries RTM locking on lock busy condition by default.
Tested with the test from bug report.
Filipp, could you run your other tests with new patch?
Thanks,
Vladimir
More information about the hotspot-compiler-dev
mailing list