java.lang.ThreadBuilders and java.lang.ThreadBuilders.newVirtualThread() are not public

[Rick Hendricksen]

Yeah, LockSupport.park(). But that’s used by other things in the JVM too, right?

- Rick

From: Alan Bateman <alan.bateman at oracle.com>
Sent: Wednesday, 21 August 2024 14:40
To: Rick Hendricksen <Rick.Hendricksen at vanderlande.com>; loom-dev at openjdk.org
Cc: Dennis van den Berg <Dennis.van.den.Berg at vanderlande.com>
Subject: Re: java.lang.ThreadBuilders and java.lang.ThreadBuilders.newVirtualThread() are not public

Be aware: This email was created outside of Vanderlande. Be cautious of its contents and do not click any links or attachments unless you recognise the sender and know the content is safe.


On 21/08/2024 11:04, Rick Hendricksen wrote:
Hi Alan,

The way we identify simulation related blocking operations is by setting a variable right before parking the thread. The scheduler then checks if that variable is null or not, and if null it was not a simulation related blocking operation and we wait until we get a simulation related blocking operation. We can get away with this because we know we are running on a single thread.

Is this LockSupport.park or blocking on something else? I'm wondering if the park blocker is set as that is something we've been mulling over whether to expose to the scheduler.

-Alan
________________________________

** Disclaimer **

This e-mail, including any attachments, may include proprietary and confidential information of Vanderlande and may only be read by the person or those persons to whom it is addressed.
This document is forwarded to you in such a form (e-mail) that Vanderlande cannot guarantee the completeness and/or correctness of its contents and information.
If you have received this e-mail message in error, please notify us immediately.
Please also delete this document from your computer.
This document may not be reproduced, copied, distributed, published, modified, or furnished to third parties, without the prior written consent of Vanderlande.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/loom-dev/attachments/20240821/6060b75f/attachment.htm>