Fri, 09 Apr 2010 13:08:34 -0400 Merge
tonyp [Fri, 09 Apr 2010 13:08:34 -0400] rev 5245
Merge
Wed, 07 Apr 2010 11:43:53 -0700 6940894: G1: assert(new_obj != 0 || ... "should be forwarded") for compaction tests
johnc [Wed, 07 Apr 2010 11:43:53 -0700] rev 5244
6940894: G1: assert(new_obj != 0 || ... "should be forwarded") for compaction tests Summary: Humongous regions may contain multiple objects as a result of being retained as to-space from a previous GC and then re-used as to-space after being tagged as humongous. These changes include a check that causes retained to-space regions that are now tagged as humongous to be disregarded and a new to-space region allocated. Reviewed-by: tonyp, iveresov
Tue, 06 Apr 2010 10:59:45 -0400 6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.")
tonyp [Tue, 06 Apr 2010 10:59:45 -0400] rev 5243
6909756: G1: guarantee(G1CollectedHeap::heap()->mark_in_progress(),"Precondition.") Summary: Make sure that two marking cycles do not overlap, i.e., a new one can only start after the concurrent marking thread finishes all its work. In the fix I piggy-back a couple of minor extra fixes: some general code reformatting for consistency (only around the code I modified), the removal of a field (G1CollectorPolicy::_should_initiate_conc_mark) which doesn't seem to be used at all (it's only set but never read), as well as moving the "is GC locker active" test earlier into the G1 pause / Full GC and using a more appropriate method for it. Reviewed-by: johnc, jmasa, jcoomes, ysr
Mon, 05 Apr 2010 12:19:22 -0400 6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop()
tonyp [Mon, 05 Apr 2010 12:19:22 -0400] rev 5242
6940310: G1: MT-unsafe calls to CM::region_stack_push() / CM::region_stack_pop() Summary: Calling the methods region_stack_push() and region_stack_pop() concurrent is not MT-safe. The assumption is that we will only call region_stack_push() during a GC pause and region_stack_pop() during marking. Unfortunately, we also call region_stack_push() during marking which seems to be introducing subtle marking failures. This change introduces lock-based methods for pushing / popping to be called during marking. Reviewed-by: iveresov, johnc
Fri, 02 Apr 2010 12:10:08 -0400 6677708: G1: re-enable parallel RSet updating and scanning
tonyp [Fri, 02 Apr 2010 12:10:08 -0400] rev 5241
6677708: G1: re-enable parallel RSet updating and scanning Summary: Enable parallel RSet updating and scanning. Reviewed-by: iveresov, jmasa
Tue, 30 Mar 2010 15:36:55 -0400 6937160: G1: should observe GCTimeRatio
tonyp [Tue, 30 Mar 2010 15:36:55 -0400] rev 5240
6937160: G1: should observe GCTimeRatio Summary: Remove the G1GCPercent parameter, that specifies the desired GC overhead percentage in G1, and observe the GCTimeRatio parameter instead. Reviewed-by: jmasa, johnc
Wed, 07 Apr 2010 12:28:22 -0400 Merge
kamg [Wed, 07 Apr 2010 12:28:22 -0400] rev 5239
Merge
Fri, 02 Apr 2010 17:04:09 -0700 Merge
jcoomes [Fri, 02 Apr 2010 17:04:09 -0700] rev 5238
Merge
Wed, 31 Mar 2010 16:51:18 -0700 6938627: Make temporary directory use property java.io.tmpdir when specified
coleenp [Wed, 31 Mar 2010 16:51:18 -0700] rev 5237
6938627: Make temporary directory use property java.io.tmpdir when specified Summary: Get java.io.tmpdir property in os::get_temp_directory() and call this instead of harcoding "/tmp". Don't assume trailing file_separator either. Reviewed-by: dholmes, kamg
Tue, 06 Apr 2010 22:06:57 -0700 Merge
asaha [Tue, 06 Apr 2010 22:06:57 -0700] rev 5236
Merge
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 +10000 +30000 tip