7051430: CMS: ongoing CMS cycle should terminate abruptly to allow prompt JVM termination at exit
Summary: It turns out that there is no need to explicitly stop CMS since the JVM is taken down at a terminal safepoint during which CMS threads are (terminally) inactive. This will need to be revised if and when we evolve in the future to a point where we allow JVM reincarnation in the same process, but those changes will be much more sweeping than just terminating CMS threads. The unused ::stop() methods will be removed in a separate CR. Also include in this CR is the fix for a small typo in the spelling of UseGCLogFileRotation in a message in arguments.cpp, brought to our attention by Rainer Jung and reviewed by minqi.
Reviewed-by: johnc, jwilhelm
author |
ysr |
date |
Mon, 13 Jun 2011 09:58:16 -0700 |
parents |
a61af66fc99e |
children |
|
rev |
line source |
0
|
1 README:
|
|
2 This file should be located at the top of the hotspot Mercurial repository.
|
|
3
|
|
4 See http://openjdk.java.net/ for more information about the OpenJDK.
|
|
5
|
|
6 See ../README-builds.html for complete details on build machine requirements.
|
|
7
|
|
8 Simple Build Instructions:
|
|
9
|
|
10 cd make && gnumake
|
|
11
|
|
12 The files that will be imported into the jdk build will be in the "build"
|
|
13 directory.
|
|
14
|