1. 14 10月, 2011 1 次提交
  2. 19 8月, 2011 1 次提交
  3. 05 3月, 2011 1 次提交
  4. 01 2月, 2011 1 次提交
    • T
      7014679: G1: deadlock during concurrent cleanup · a54411a3
      tonyp 提交于
      Summary: There's a potential deadlock between the concurrent cleanup thread and the GC workers that are trying to allocate and waiting for more free regions to be made available.
      Reviewed-by: iveresov, jcoomes
      a54411a3
  5. 22 1月, 2011 1 次提交
    • T
      7013718: G1: small fixes for two assert/guarantee failures · d2d605ca
      tonyp 提交于
      Summary: Two small fixes to deal with a guarantee failure (the marking thread should join the SuspendibleThreadSet before calling a method that does pause prediction work so that said method is never called during a pause) and an assert failure (an assert is too strong).
      Reviewed-by: iveresov, johnc
      d2d605ca
  6. 20 1月, 2011 1 次提交
    • T
      6977804: G1: remove the zero-filling thread · 0ed267ef
      tonyp 提交于
      Summary: This changeset removes the zero-filling thread from G1 and collapses the two free region lists we had before (the "free" and "unclean" lists) into one. The new free list uses the new heap region sets / lists abstractions that we'll ultimately use it to keep track of all regions in the heap. A heap region set was also introduced for the humongous regions. Finally, this change increases the concurrency between the thread that completes freeing regions (after a cleanup pause) and the rest of the system (before we'd have to wait for said thread to complete before allocating a new region). The changest also includes a lot of refactoring and code simplification.
      Reviewed-by: jcoomes, johnc
      0ed267ef
  7. 15 12月, 2010 1 次提交
    • T
      7000559: G1: assertion failure !outer || (full_collections_started ==... · 49b4b500
      tonyp 提交于
      7000559: G1: assertion failure !outer || (full_collections_started == _full_collections_completed + 1)
      Summary: The concurrent marking thread can complete its operation and increment the full GC counter during a Full GC. This causes the nesting of increments to the start and end of Full GCs that we are expecting to be wrong. the fix is for the marking thread to join the suspendible thread set before incrementing the counter so that it's blocked until the Full GC (or any other safepoint) is finished. The change also includes some minor code cleanup (I renamed a parameter).
      Reviewed-by: brutisso, ysr
      49b4b500
  8. 24 11月, 2010 1 次提交
  9. 02 10月, 2010 1 次提交
    • J
      6983311: G1: LoopTest hangs when run with -XX:+ExplicitInvokesConcurrent · 52b8d7bd
      johnc 提交于
      Summary: Clear the concurrent marking "in progress" flag while the FullGCCount_lock is held. This avoids a race that can cause back to back System.gc() calls, when ExplicitGCInvokesConcurrent is enabled, to fail to initiate a marking cycle causing the requesting thread to hang.
      Reviewed-by: tonyp, ysr
      52b8d7bd
  10. 29 6月, 2010 1 次提交
  11. 28 5月, 2010 1 次提交
  12. 03 10月, 2009 1 次提交
    • T
      6885041: G1: inconsistent thread dump · 510d088c
      tonyp 提交于
      Summary: When G1 is enabled, thread dumps are inconsistent as the info for some of the G1 threads is not formatted properly.
      Reviewed-by: ysr, johnc
      510d088c
  13. 20 8月, 2009 1 次提交
    • T
      6871111: G1: remove the concurrent overhead tracker · 228aaca7
      tonyp 提交于
      Summary: Removing the concurrent overhead tracker from G1, along with the GC overhead reporter and the G1AccountConcurrentOverhead (both of which rely on the the concurrent overhead tracker).
      Reviewed-by: iveresov, johnc
      228aaca7
  14. 29 7月, 2009 1 次提交
    • X
      6862919: Update copyright year · 84c0f327
      xdono 提交于
      Summary: Update copyright for files that have been modified in 2009, up to 07/09
      Reviewed-by: tbell, ohair
      84c0f327
  15. 01 5月, 2009 1 次提交
  16. 08 3月, 2009 1 次提交
  17. 06 6月, 2008 1 次提交