changeset 38638:c053db913695

8149901: [Solaris] Use of -XX:+UseThreadPriorities crashes fastdebug Reviewed-by: gziemski, sspitsyn
author dholmes
date Fri, 20 May 2016 01:47:32 -0400
parents dba1e7561542
children 470ee64d4a67 3444f0668c83
files hotspot/src/os/solaris/vm/os_solaris.cpp
diffstat 1 files changed, 7 insertions(+), 9 deletions(-) [+]
line wrap: on
line diff
--- a/hotspot/src/os/solaris/vm/os_solaris.cpp	Thu May 19 10:48:28 2016 -0400
+++ b/hotspot/src/os/solaris/vm/os_solaris.cpp	Fri May 20 01:47:32 2016 -0400
@@ -756,15 +756,9 @@
     }
   }
 
-  // If the creator called set priority before we started,
-  // we need to call set_native_priority now that we have an lwp.
-  // We used to get the priority from thr_getprio (we called
-  // thr_setprio way back in create_thread) and pass it to
-  // set_native_priority, but Solaris scales the priority
-  // in java_to_os_priority, so when we read it back here,
-  // we pass trash to set_native_priority instead of what's
-  // in java_to_os_priority. So we save the native priority
-  // in the osThread and recall it here.
+  // Our priority was set when we were created, and stored in the
+  // osthread, but couldn't be passed through to our LWP until now.
+  // So read back the priority and set it again.
 
   if (osthr->thread_id() != -1) {
     if (UseThreadPriorities) {
@@ -1044,6 +1038,10 @@
   // Remember that we created this thread so we can set priority on it
   osthread->set_vm_created();
 
+  // Most thread types will set an explicit priority before starting the thread,
+  // but for those that don't we need a valid value to read back in thread_native_entry.
+  osthread->set_native_priority(NormPriority);
+
   // Initial thread state is INITIALIZED, not SUSPENDED
   osthread->set_state(INITIALIZED);