From 6355dec98c070dafdc3e697445a2e3bab56b8b66 Mon Sep 17 00:00:00 2001 From: Kim Barrett Date: Thu, 16 Aug 2018 19:49:25 -0400 Subject: [PATCH] 8209607: Remove stale comment for JNI mutexes Remove comment. Reviewed-by: dholmes --- src/hotspot/share/runtime/mutexLocker.cpp | 5 ----- 1 file changed, 5 deletions(-) diff --git a/src/hotspot/share/runtime/mutexLocker.cpp b/src/hotspot/share/runtime/mutexLocker.cpp index 380f3e4c1e5..316e1251180 100644 --- a/src/hotspot/share/runtime/mutexLocker.cpp +++ b/src/hotspot/share/runtime/mutexLocker.cpp @@ -263,11 +263,6 @@ void mutex_init() { def(Terminator_lock , PaddedMonitor, nonleaf, true, Monitor::_safepoint_check_sometimes); def(VtableStubs_lock , PaddedMutex , nonleaf, true, Monitor::_safepoint_check_always); def(Notify_lock , PaddedMonitor, nonleaf, true, Monitor::_safepoint_check_always); - // OopStorage-based JNI may lock the alloc_locks while releasing a handle, - // while previous JNI didn't need a lock for handle release. This runs afoul - // of some places which hold other locks while releasing a handle, including - // the Patching_lock, which is of "special" rank. As a temporary workaround, - // lower the JNI oopstorage lock ranks to make them super-special. def(JNIGlobalAlloc_lock , PaddedMutex , nonleaf, true, Monitor::_safepoint_check_never); def(JNIGlobalActive_lock , PaddedMutex , nonleaf-1, true, Monitor::_safepoint_check_never); def(JNIWeakAlloc_lock , PaddedMutex , nonleaf, true, Monitor::_safepoint_check_never);