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

Remove suspend_flag

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: 15
    • Fix Version/s: tbd
    • Component/s: hotspot
    • Labels:

      Description

      Removing _suspend_flag and has_special_runtime_exit_condition/handle_special_runtime_exit_condition and friends will greatly simplify transition and will make it possible to contain the functionality.
      Right now it's spread out all over the runtime and we have many special transition for not getting this wrong.
      Delivery conditions are duplicate and very hard to understand.

      The _suspend_flag is asynchronous and target executed:
      Set bit X and thread execute method Y when doing a transition where the delivery terms are met.

      Since we already have a safepoint(/handshake) poll at every possible delivery location, these can be implementerad as handshake (if we had the correct functionality).
      The handshake operation could contain both the delivery terms and the delivery, thus having everything at one place and only once.

      There are now 4 (soon 5) users:
        - Suspend/resume
        - Delivering Asynchronous exception (ThreadDeath)
        - Lazy JNI critical unlocking
        - JFR Native trace blocking
        - Local variable reconstitution

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              rehn Robbin Ehn
              Reporter:
              rehn Robbin Ehn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated: