RFR: 8199717: Avoid calculating primordial thread stack bounds on VM startup

David Holmes david.holmes at oracle.com
Wed Mar 28 11:19:02 UTC 2018


On 28/03/2018 7:51 AM, David Holmes wrote:
> Hi Claes,
> 
> I was concerned that this change prevents the primordial thread from 
> being able to attach to a VM created on a new thread. But I suppose we 
> must assume that if created_by_java_launcher is true then:
> 
> a) the VM was not created by the primordial thread; and
> b) the primordial thread will not attach to the VM
> 
> I still need to check this with the R-Java folk (as the only case I know 
> where the VM is created on the primordial thread).

Tomas Kalibera has confirmed this is not a problem for them.

Cheers,
David

> Thanks,
> David
> 
> On 28/03/2018 4:35 AM, Thomas Stüfe wrote:
>> On Tue, Mar 27, 2018 at 3:43 PM, Claes Redestad 
>> <claes.redestad at oracle.com>
>> wrote:
>>
>>> On 2018-03-27 15:33, Thomas Stüfe wrote:
>>>
>>> maybe "suppress_primordial_thread_resolution"
>>>>
>>>>
>>> Sure that makes more sense!
>>>
>>>
>>> Ok: http://cr.openjdk.java.net/~redestad/8199717/open.01/
>>>
>>> /Claes
>>>
>>
>> Beautiful comment, thank you :)
>>
>> All is fine.
>>
>> Thanks, Thomas
>>


More information about the hotspot-runtime-dev mailing list