Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8276824

refactor Thread::is_JavaThread_protected

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 18
    • Fix Version/s: 18
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b24
    • CPU:
      generic
    • OS:
      generic

      Description

      During the code review for the following RFE:

          JDK-8249004 Reduce ThreadsListHandle overhead in relation to direct handshakes

      [~coleenp] mentioned that she was not happy about the
      "bool checkTLHOnly" parameter that was added to
      Thread::is_JavaThread_protected(). The new parameter
      basically turned Thread::is_JavaThread_protected() into
      two different functions with the decision on which one to
      execute based on the new parameter. She would prefer
      to refactor Thread::is_JavaThread_protected() into two
      functions and have Thread::is_JavaThread_protected()
      call the new function for the portion of the logic that was
      moved.

      The new calls to Thread::is_JavaThread_protected() that
      passed "true" for the second parameter would change to
      call the new function.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dcubed Daniel Daugherty
              Reporter:
              dcubed Daniel Daugherty
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: