hg: jdk7/hotspot/hotspot: 8 new changesets
john.coomes at oracle.com
john.coomes at oracle.com
Mon Nov 1 23:48:33 PDT 2010
Changeset: 35e4e086d5f5
Author: tonyp
Date: 2010-10-14 10:38 -0400
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/35e4e086d5f5
6990359: G1: don't push a stolen entry on the taskqueue, deal with it directly
Summary: When an entry is stolen, don't push it on the task queue but process it directly.
Reviewed-by: iveresov, ysr, jcoomes
! src/share/vm/gc_implementation/g1/g1CollectedHeap.cpp
! src/share/vm/gc_implementation/g1/g1CollectedHeap.hpp
Changeset: 9f4848ebbabd
Author: tonyp
Date: 2010-10-15 17:26 -0400
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/9f4848ebbabd
6992189: G1: inconsistent base used in sparse rem set iterator
Summary: The remembered set iterator for sparse tables incorrectly assumes that index 0 corresponds to the bottom of the heap, not address 0 as it is the case.
Reviewed-by: ysr, jmasa
! src/share/vm/gc_implementation/g1/heapRegionRemSet.cpp
! src/share/vm/gc_implementation/g1/sparsePRT.cpp
! src/share/vm/gc_implementation/g1/sparsePRT.hpp
Changeset: a5c514e74487
Author: johnc
Date: 2010-10-18 15:01 -0700
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/a5c514e74487
6988458: G1: assert(mr.end() <= _cm->finger()) failed: otherwise the region shouldn't be on the stack
Summary: The changes from 6941395 did not clear the CMTask::_aborted_region fields when concurrent marking aborted because of overflow. As a result, the next time around we could see a memory region whose start address was above the global finger and the assertion tripped. Moved the clearing of the aborted regions to ConcurrentMark::clear_marking_state, which is executed on all of the exit paths.
Reviewed-by: tonyp, ysr, jmasa
! src/share/vm/gc_implementation/g1/concurrentMark.cpp
Changeset: 72a161e62cc4
Author: tonyp
Date: 2010-10-16 17:12 -0400
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/72a161e62cc4
6991377: G1: race between concurrent refinement and humongous object allocation
Summary: There is a race between the concurrent refinement threads and the humongous object allocation that can cause the concurrent refinement threads to corrupt the part of the BOT that it is being initialized by the humongous object allocation operation. The solution is to do the humongous object allocation in careful steps to ensure that the concurrent refinement threads always have a consistent view over the BOT, region contents, and top. The fix includes some very minor tidying up in sparsePRT.
Reviewed-by: jcoomes, johnc, ysr
! src/share/vm/gc_implementation/g1/g1BlockOffsetTable.cpp
! src/share/vm/gc_implementation/g1/g1BlockOffsetTable.hpp
! src/share/vm/gc_implementation/g1/heapRegion.cpp
! src/share/vm/gc_implementation/g1/heapRegion.hpp
! src/share/vm/gc_implementation/g1/heapRegionSeq.cpp
! src/share/vm/gc_implementation/g1/sparsePRT.cpp
! src/share/vm/gc_implementation/g1/sparsePRT.hpp
Changeset: cd3ef3fd20dd
Author: ysr
Date: 2010-10-21 17:29 -0700
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/cd3ef3fd20dd
6992998: CMSWaitDuration=0 causes hangs with +ExplicitGCInvokesConcurrent
Summary: Closed a timing hole during which concurrent full gc requests can be missed. The hole can increase the latency of the response to a full gc request by up to the value of CMSWaitDuration. If CMSWaitDuration=0 is, as currently, interpreted as an unbounded wait, suitable in certain tuning scenarios, the application can potentially hang. Made two obscure tunables, including CMSWaitDuration, manageable.
Reviewed-by: jcoomes, tonyp
! src/share/vm/gc_implementation/concurrentMarkSweep/concurrentMarkSweepThread.cpp
! src/share/vm/gc_implementation/concurrentMarkSweep/concurrentMarkSweepThread.hpp
! src/share/vm/runtime/globals.hpp
Changeset: a7214d79fcf1
Author: ysr
Date: 2010-10-23 23:03 -0700
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/a7214d79fcf1
6896603: CMS/GCH: collection_attempt_is_safe() ergo should use more recent data
Summary: Deprecated HandlePromotionFailure, removing the ability to turn off that feature, did away with one epoch look-ahead when deciding if a scavenge is likely to fail, relying on current data.
Reviewed-by: jmasa, johnc, poonam
! src/share/vm/gc_implementation/concurrentMarkSweep/concurrentMarkSweepGeneration.cpp
! src/share/vm/gc_implementation/concurrentMarkSweep/concurrentMarkSweepGeneration.hpp
! src/share/vm/gc_implementation/parNew/parNewGeneration.cpp
! src/share/vm/memory/collectorPolicy.cpp
! src/share/vm/memory/defNewGeneration.cpp
! src/share/vm/memory/defNewGeneration.hpp
! src/share/vm/memory/genCollectedHeap.cpp
! src/share/vm/memory/genCollectedHeap.hpp
! src/share/vm/memory/generation.cpp
! src/share/vm/memory/generation.hpp
! src/share/vm/memory/tenuredGeneration.cpp
! src/share/vm/memory/tenuredGeneration.hpp
! src/share/vm/runtime/arguments.cpp
! src/share/vm/runtime/globals.hpp
Changeset: c766bae6c14d
Author: ysr
Date: 2010-10-28 14:46 -0700
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/c766bae6c14d
6995045: assert(!gch->incremental_collection_failed()) failed: Error, defNewGeneration.cpp:827
Summary: Sharpened an assert, introduced in 6896603, that intended to check that the incremental_collection_failed() predicate on the heap was being reset "soon enough".
Reviewed-by: jmasa
! src/share/vm/memory/defNewGeneration.cpp
Changeset: f5c8d6e5bfee
Author: jcoomes
Date: 2010-11-01 10:49 -0700
URL: http://hg.openjdk.java.net/jdk7/hotspot/hotspot/rev/f5c8d6e5bfee
Merge
! src/share/vm/runtime/arguments.cpp
! src/share/vm/runtime/globals.hpp
More information about the jdk7-changes
mailing list