trims [Fri, 11 Dec 2009 16:38:37 -0800] rev 4467
Merge
jmasa [Fri, 11 Dec 2009 08:39:30 -0800] rev 4466
Merge
ysr [Tue, 08 Dec 2009 15:12:17 -0800] rev 4465
6908208: UseCompressedOops: array_size() returns incorrect size for MAX_INT object array following 6906727
Summary: In array_size() cast to an unsigned to avoid overflow of intermediate value.
Reviewed-by: kvn, tonyp, jmasa, jcoomes, coleenp
tonyp [Mon, 07 Dec 2009 14:22:34 -0500] rev 4464
6904967: G1: some CollectionUsageThreshold tests fail
Summary: ensure that max and committed are non-zero (currently: at least as large as the region size).
Reviewed-by: iveresov, mchung
tonyp [Fri, 04 Dec 2009 07:44:41 -0500] rev 4463
6906565: G1: deal with compilation warning in g1MemoryPool.hpp
Summary: size_t max_size() hides size_t max_size() const.
Reviewed-by: jmasa, ysr
tonyp [Fri, 04 Dec 2009 07:44:35 -0500] rev 4462
6880903: G1: G1 reports incorrect Runtime.maxMemory()
Summary: G1 reports committed memory instead of reserved memory from the Runtime.maxMemory() method
Reviewed-by: ysr, jmasa
ysr [Thu, 03 Dec 2009 15:01:57 -0800] rev 4461
6906727: UseCompressedOops: some card-marking fixes related to object arrays
Summary: Introduced a new write_ref_array(HeapWords* start, size_t count) method that does the requisite MemRegion range calculation so (some of the) clients of the erstwhile write_ref_array(MemRegion mr) do not need to worry. This removed all external uses of array_size(), which was also simplified and made private. Asserts were added to catch other possible issues. Further, less essential, fixes stemming from this investigation are deferred to CR 6904516 (to follow shortly in hs17).
Reviewed-by: kvn, coleenp, jmasa
johnc [Tue, 24 Nov 2009 15:19:30 -0800] rev 4460
6899058: G1: Internal error in ptrQueue.cpp:201 in nightly tests
Summary: Fixes a race on the dirty card queue completed buffer list between worker thread(s) performing a flush of a deferred store barrier (enqueueing a newly completed buffer) and worker thread(s) in the RSet updating code claiming completed buffers. Removed the routine that removes elements from the completed update buffer queue using a CAS.
Reviewed-by: ysr, tonyp
tonyp [Fri, 20 Nov 2009 14:47:01 -0500] rev 4459
6815790: G1: Missing MemoryPoolMXBeans with -XX:+UseG1GC
Summary: It introduces the necessary memory pools for G1.
Reviewed-by: mchung, ysr
ysr [Thu, 19 Nov 2009 13:43:25 -0800] rev 4458
6902303: G1: ScavengeALot should cause an incremental, rather than a full, collection
Summary: ScavengeALot now causes an incremental (but possibly partially young, in the G1 sense) collection. Some such collections may be abandoned on account of MMU specs. Band-aided a native leak associated with abandoned pauses, as well as an MMU tracker overflow related to frequent scavenge events in the face of a large MMU denominator interval; the latter is protected by a product flag that defaults to false.
Reviewed-by: tonyp
ysr [Thu, 19 Nov 2009 10:19:19 -0800] rev 4457
6902701: G1: protect debugging code related to 6898948 with a debug flag
Summary: Protected stats dump with a new develop flag; other than for the dump, reconciled product and non-product behaviour in face of the error.
Reviewed-by: tonyp
ysr [Fri, 13 Nov 2009 11:55:26 -0800] rev 4456
6898948: G1: forensic instrumentation for out-of-bounds recent_avg_pause_time_ratio()
Summary: Added instrumentation and (temporary) assert in non-product mode; clipped the value when found out-of-bounds in product mode. Fix of original issue will follow collection of data from this instrumentation.
Reviewed-by: jcoomes, tonyp
jmasa [Tue, 10 Nov 2009 11:32:48 -0800] rev 4455
6898857: [Regression] -XX:NewRatio with -XX:+UseConcMarkSweepGC causes fatal error
Summary: Use CollectorPolicy information instead of MaxNewSize
Reviewed-by: ysr, jcoomes
johnc [Fri, 06 Nov 2009 11:10:05 -0800] rev 4454
6895788: G1: SATB and update buffer allocation code allocates too much space
Summary: The type in the NEW_C_HEAP_ARRRY and FREE_C_HEAP_ARRAY calls in the buffer allocation code was changed from void* to char as the size argument had already been mulitipled by the byte size of an object pointer.
Reviewed-by: ysr, tonyp