RFR: 8205053: Decouple type registration from framework lifecycle
Per Liden
per.liden at oracle.com
Tue Jun 19 21:29:04 UTC 2018
What part of JFR needs to be initialized before I can start to make
calls to JfrSerializer::register_serializer()? Looks like
Jfr::on_vm_init() is called fairly late (like long after the heap has
been initialized), but I'm not sure if that needs to be called before
other subsystems can start registering serializes?
/Per
On 06/19/2018 10:58 PM, Erik Gahlin wrote:
> Hi,
>
> Could I have review of a fix that makes it possible to register
> checkpoint serializers independent of the JFR lifecycle. This is so
> registration can happen close to where a particular subsystem is
> initialized. For instance, the registration of the compiler phase type
> and its serialization could happen where the compiler is initialized.
>
> Webrev:
> http://cr.openjdk.java.net/~egahlin/8205053/
>
> Bug:
> https://bugs.openjdk.java.net/browse/JDK-8205053
>
> Testing:
> Tests in test/jdk/jdk/jfr
>
> Thanks
> Erik
More information about the hotspot-jfr-dev
mailing list