JDK-8213524 : SafepointMechanism: poor method naming
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 12
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2018-11-08
  • Updated: 2024-01-10
  • Resolved: 2024-01-10
Related Reports
Relates :  
JDK-8252661 - Change SafepointMechanism terminology to talk less about "blocking"
Relates :  
JDK-8220051 - Remove global safepoint code
Description
SafepointMechanism having most method called something with poll and many prefixed with global or local indicates that we do not have a clear design and calling everything poll also seem to indicate that we are using a poor terminology.
Comments
Runtime Triage: This is not on our current list of priorities. We will consider this feature if we receive additional customer requirements.
10-01-2024
This code will be revisited in 14 for the obsoleting of global polling code, I suggest we look at this then.
28-03-2019
The original safepoint mechanism already has some mis-named methods that didn't really reflect what they did. Since adding the per-thread local polls we've now got two sets of methods. There's a lot of scope for cleaning this up.
08-11-2018