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

G1: Rework VM_G1Concurrent VMOp to clearly identify it as pause

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 11, 17, 18, 19
    • Fix Version/s: 19
    • Component/s: hotspot
    • Subcomponent:
      gc
    • Resolved In Build:
      master

      Description

      Our support engineers asked this:

      > I see these G1Concurrent safepoints in JDK17:
      > [0.064s][info][safepoint ] Safepoint "G1Concurrent", Time since last: 1666947 ns, Reaching
      safepoint: 79150 ns, At safepoint: 349999 ns, Total: 429149 ns
      > I've always thought that "concurrent" and "safepoint" are basically antonyms.
      > What is a G1Concurrent safepoint? How can a concurrent event require a safepoint?

      I think the naming here is unfortunate:
      https://github.com/openjdk/jdk/blob/b79554bb5cef14590d427543a40efbcc60c66548/src/hotspot/share/gc/g1/g1VMOperations.hpp#L89-L103

      ...and we can clean that up a bit. I'll propose a patch.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              shade Aleksey Shipilev
              Reporter:
              shade Aleksey Shipilev
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: