Pls review (S) 7117389: Add a framework for vendor-specific command line switch extensions to Hotspot

Paul Hohensee paul.hohensee at oracle.com
Mon Dec 5 06:44:03 PST 2011


Yes, you'd have to have your own build.  Oracle does this now.  OpenJDK
builds are slightly different from OracleJDK ones right now and we expect
that to continue going forward.

Paul

On 12/3/11 8:01 AM, Charles K Pepperdine wrote:
> Hi Paul,
>
> Does this imply that if I wanted to add a command line switch for my commercial product that was "embedded" into the JVM I would have to do this in a special build? I'm trying to sort out how this would work?
>
> Regards,
> Kirk
>
> On Dec 2, 2011, at 4:54 PM, Paul Hohensee wrote:
>
>> Webrev here:
>>
>> http://cr.openjdk.java.net/~phh/7117389/
>>
>> This webrev defines and uses, but does not implement, a switch extension interface.
>>
>> I've added a new file, globals_ext.hpp, that contains hooks for vendor-specific additions
>> to the set of Hotspot command line switches and added their use to globals.hpp,
>> globals.cpp and globals_extension.hpp.  I chose "_ext" as a generic suffix for files
>> containing extension hooks.  In effect, such files are interface definitions.  A vendor
>> supplies a file, perhaps of the same name in another source base (as can be seen in
>> the Hotspot makefiles), that implements the extension hooks.
>>
>> Thanks,
>>
>> Paul
>>


More information about the hotspot-dev mailing list