Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Implementation of SATB routines to enable SATB for `optavgpause` _(Limited to Xint+OOL Allocations)_ - Added obj alloc premarking to TLH Allocation interface - Introduced some ASSERTS in shared ConcurrentGC code to ensure we don't transition to certain concurrent sates and we don't call certain callbacks known to be unreachable by SATB _Implemented the following methods for SATB collector:_ - `setupForConcurrent` - initial STW to mark roots and set allocation colour - `doConcurrentTrace` - trace routine, adapted from incremental approach simplified to remove CARDS and "promote" Background threads activity - `completeConcurrentTracing`- final STW to flush barrier packets and complete any remaining tracing before handing off to ParallelGlobalGC - `setThreadsScanned` - to shade threads "black" - `initialize`; currently there is much this method does, but will be needed to register call backs for GENCON and premaking TLH Signed-off-by: Salman Rana <salman.rana@ibm.com>
- Loading branch information
Showing
14 changed files
with
215 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.