1. 03 1月, 2013 1 次提交
  2. 01 12月, 2012 1 次提交
  3. 28 11月, 2012 1 次提交
  4. 27 11月, 2012 1 次提交
  5. 16 10月, 2012 1 次提交
  6. 10 10月, 2012 1 次提交
  7. 09 10月, 2012 1 次提交
  8. 06 10月, 2012 1 次提交
  9. 05 10月, 2012 1 次提交
  10. 04 10月, 2012 1 次提交
  11. 02 10月, 2012 1 次提交
  12. 28 9月, 2012 1 次提交
    • J
      7200261: G1: Liveness counting inconsistencies during marking verification · ebc0255b
      johnc 提交于
      Summary: The clipping code in the routine that sets the bits for a range of cards, in the liveness accounting verification code was incorrect. It set all the bits in the card bitmap from the given starting index which would lead to spurious marking verification failures.
      Reviewed-by: brutisso, jwilhelm, jmasa
      ebc0255b
  13. 25 9月, 2012 2 次提交
  14. 21 9月, 2012 1 次提交
    • J
      7190666: G1: assert(_unused == 0) failed: Inconsistency in PLAB stats · 749cb85e
      johnc 提交于
      Summary: Reset the fields in ParGCAllocBuffer, that are used for accumulating values for the ResizePLAB sensors in PLABStats, to zero after flushing the values to the PLABStats fields. Flush PLABStats values only when retiring the final allocation buffers prior to disposing of a G1ParScanThreadState object, rather than when retiring every allocation buffer.
      Reviewed-by: jwilhelm, jmasa, ysr
      749cb85e
  15. 20 9月, 2012 1 次提交
    • J
      7193946: Move warnings associated with UseMemSetInBOT flag · 4bf72cf2
      johnc 提交于
      Summary: The warnings associated with the UseMemSetInBOT flag are duplicated in CMS and G1. The separate warnings have been removed and single instance of the warning has been placed in a common location.
      Reviewed-by: brutisso, ysr
      4bf72cf2
  16. 19 9月, 2012 1 次提交
  17. 17 9月, 2012 2 次提交
  18. 14 9月, 2012 1 次提交
  19. 02 9月, 2012 1 次提交
  20. 29 8月, 2012 1 次提交
    • J
      7041879: G1: introduce stress testing parameter to cause frequent evacuation failures · 3c3c2c12
      johnc 提交于
      Summary: Add the flags G1EvacuationFailureALot flag (and supporting flags) to force trigger evacuation failures. The support flags control how often to trigger an evacuation failure and during which types of evacuation pause. This functionality is analogous to that of PromotionFailureALot for the other collectors.
      Reviewed-by: brutisso
      3c3c2c12
  21. 23 8月, 2012 2 次提交
  22. 22 8月, 2012 2 次提交
    • J
      7185699: G1: Prediction model discrepancies · 4e8955cf
      johnc 提交于
      Summary: Correct the result value of G1CollectedHeap::pending_card_num(). Change the code that calculates the GC efficiency of a non-young heap region to use historical data from mixed GCs and the actual number of live bytes when predicting how long it would take to collect the region. Changes were also reviewed by Thomas Schatzl.
      Reviewed-by: azeemj, brutisso
      4e8955cf
    • J
      7192128: G1: Extend fix for 6948537 to G1's BOT · ddfab1b9
      johnc 提交于
      Summary: G1 does not appear to be immune to the issue described in CR 6948537 and increasing the size of old-generation PLABs appears to increase the liklihood of seeing the issue. Extend the fix for 6948537 to G1's BlockOffsetTable.
      Reviewed-by: brutisso, jmasa
      ddfab1b9
  23. 07 8月, 2012 1 次提交
  24. 20 7月, 2012 1 次提交
  25. 18 7月, 2012 3 次提交
  26. 12 7月, 2012 1 次提交
  27. 29 6月, 2012 1 次提交
    • Z
      6995781: Native Memory Tracking (Phase 1) · bdfb3cf5
      zgu 提交于
      7151532: DCmd for hotspot native memory tracking
      Summary: Implementation of native memory tracking phase 1, which tracks VM native memory usage, and related DCmd
      Reviewed-by: acorn, coleenp, fparain
      bdfb3cf5
  28. 26 6月, 2012 1 次提交
  29. 04 6月, 2012 1 次提交
  30. 06 6月, 2012 1 次提交
  31. 01 6月, 2012 1 次提交
  32. 26 5月, 2012 1 次提交
  33. 30 5月, 2012 1 次提交
    • J
      7143858: G1: Back to back young GCs with the second GC having a minimally sized eden · 893ceddc
      johnc 提交于
      Summary: Before the last thread to leave a JNI critical region was able to schedule a GCLocker Initiated GC, another thread was attempting an allocation and saw that the GCLocker region was no longer active and successfully scheduled a GC. Stall allocating threads until the GCLocker Initiated GC is performed and then retry the allocation.
      Reviewed-by: brutisso, huntch
      893ceddc
  34. 15 5月, 2012 1 次提交