src/hotspot/share/code/codeHeapState.cpp

rev 54096 : 8214526: Change CodeHeap State Analytics control from UL to Print*
Reviewed-by: coleenp, kvn, stuefe, thartmann

*** 36,46 ****
  // information that is believed useful/important.
  //
  // Aggregation condenses the information of a piece of the CodeHeap
  // (4096 bytes by default) into an analysis granule. These granules
  // contain enough detail to gain initial insight while keeping the
! // internal sttructure sizes in check.
  //
  // The CodeHeap is a living thing. Therefore, the aggregate is collected
  // under the CodeCache_lock. The subsequent print steps are only locked
  // against concurrent aggregations. That keeps the impact on
  // "normal operation" (JIT compiler and sweeper activity) to a minimum.
--- 36,46 ----
  // information that is believed useful/important.
  //
  // Aggregation condenses the information of a piece of the CodeHeap
  // (4096 bytes by default) into an analysis granule. These granules
  // contain enough detail to gain initial insight while keeping the
! // internal structure sizes in check.
  //
  // The CodeHeap is a living thing. Therefore, the aggregate is collected
  // under the CodeCache_lock. The subsequent print steps are only locked
  // against concurrent aggregations. That keeps the impact on
  // "normal operation" (JIT compiler and sweeper activity) to a minimum.
*** 61,79 ****
  // Requests for real-time, on-the-fly analysis can be issued via
  //   jcmd <pid> Compiler.CodeHeap_Analytics [<function>] [<granularity>]
  //
  // If you are (only) interested in how the CodeHeap looks like after running
  // a sample workload, you can use the command line option
! //   -Xlog:codecache=Trace
  //
! // To see the CodeHeap state in case of a "CodeCache full" condition, start the
! // VM with the
! //   -Xlog:codecache=Debug
! // command line option. It will produce output only for the first time the
! // condition is recognized.
! //
! // Both command line option variants produce output identical to the jcmd function
  //   jcmd <pid> Compiler.CodeHeap_Analytics all 4096
  // ---------------------------------------------------------------------------------
  
  // With this declaration macro, it is possible to switch between
  //  - direct output into an argument-passed outputStream and
--- 61,76 ----
  // Requests for real-time, on-the-fly analysis can be issued via
  //   jcmd <pid> Compiler.CodeHeap_Analytics [<function>] [<granularity>]
  //
  // If you are (only) interested in how the CodeHeap looks like after running
  // a sample workload, you can use the command line option
! //   -XX:+PrintCodeHeapAnalytics
! // It will cause a full analysis to be written to tty. In addition, a full
! // analysis will be written the first time a "CodeCache full" condition is
! // detected.
  //
! // The command line option produces output identical to the jcmd function
  //   jcmd <pid> Compiler.CodeHeap_Analytics all 4096
  // ---------------------------------------------------------------------------------
  
  // With this declaration macro, it is possible to switch between
  //  - direct output into an argument-passed outputStream and