G1: Introduce safer STS join/leave (and vice versa) critical sections

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Duplicate
    • Priority: P4
    • 9.1
    • Affects Version/s: hs23
    • Component/s: hotspot
    • gc
    • generic
    • generic

      In G1 there are many places where code is bracketed by calls to SuspendibleThreadSet::join() and SuspendibleThreadSet::leave() (and vice versa).

      It'd be helpful to introduce two classes that automatically ensure that the appropriate action is taken at the start and end of such a critical section using the standard idiom of calling the appropriate method in the constructor and destructor of each class (similar to how MutexLocker / MutexUnlocker work).

            Assignee:
            Unassigned
            Reporter:
            Tony Printezis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: