On Tue, 28 Oct 2025 14:30:42 GMT, Dan Heidinga <[email protected]> wrote:
>> Add jdk.management.AOTCacheMXBean. The interface provides a single action >> that when called will cause any hosted JVM currently recording AOT >> information will stop recording. Existing functionality is preserved: when >> stopped the JVM will create the required artifacts based on the execution >> mode. Conveniently as the application running on the JVM has not stopped (as >> was previously the only way to stop recording), the application will resume >> execution after the artifacts have been generated. >> >> The interface will return TRUE if a recording was successfully stopped, in >> all other cases (not recording etc.) will return FALSE >> >> It follows that invoking the action on a JVM that is recording, twice in >> succession, should (baring internal errors) produce the following two >> responses: >> >> TRUE >> FALSE >> >> Passes tier1 on linux (x64) and windows (x64) > > src/jdk.management/share/classes/jdk/management/HotSpotAOTCacheMXBean.java > line 34: > >> 32: >> 33: /** >> 34: * Management interface for the JDK's Ahead of Time (AOT) optimizations. > > I don't like the word "optimizations" here but don't have a better one. > Maybe "operation"? Still not great Well, one possible alternative is kind of implicit in the bean name: "Management interface for the JDK's Ahead of Time (AOT) Cache" ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/28010#discussion_r2470201352
