RFR: 8073464 - GC workers do not have thread names
charlie hunt
charlie.hunt at oracle.com
Fri Feb 20 13:50:41 UTC 2015
Nice to see this implemented!
A next enhancement I would really like to see implemented is a JVMTI
event that makes available all JVM internal thread names. That would
enable us to see internal JVM thread names in profilers like Studio
Analyzer.
I realize the JVMTI events fall under a different area than GC. But,
thought the enhancement was worth mentioning given this change.
thanks,
charlie
On 02/20/2015 07:39 AM, David Lindholm wrote:
> Hi,
>
> Please review this small fix in GangWorker:initialize(). This addition
> sets the native thread names of GangWorker threads, which the GC uses
> for worker threads. Now these names will be visible when debugging in
> GDB.
>
> Webrev:
> http://cr.openjdk.java.net/~stefank/0thers/david/8073464/webrev.00/
> Bug: https://bugs.openjdk.java.net/browse/JDK-8073464
>
>
> Thanks,
> David
>
>
More information about the hotspot-gc-dev
mailing list