RFR: 8371409: Wrong lock ordering between FullGCALot_lock and ThreadsLockT… d0522e9 …hrottle_lock/MethodCompileQueue_lock

[Robbin Ehn]

On Wed, 3 Dec 2025 12:59:34 GMT, Coleen Phillimore <coleenp at openjdk.org> wrote:

> This changes the rank of FullGCALot_lock to nosafepoint since it's taken when we want to do FullGCALot when we take safepoint lock so should always be a rank below that.  This lock is very limited in what it does - it only protects some memory that we allocate at the bottom/beginning of the heap so that full gc with older collectors has to move stuff.
> Tested with tier1-4.  I wrote a test case where I verified this change but the test case times out, so noreg-hard.

This makes sense, thanks @coleenp !

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

Marked as reviewed by rehn (Reviewer).

PR Review: https://git.openjdk.org/jdk/pull/28633#pullrequestreview-3535241250