On Wed, 21 May 2025 20:35:33 GMT, Alex Menkov <amen...@openjdk.org> wrote:
> The change fixes "Thread.print" diagnostic command when mounted virtual > thread is waiting on the class initialization monitor. > > Testing: new test, tier1 sanity run To me, in the pinned case, both threads are "really waiting". The carrier physically and the vthread "logically". This also indicates it is actually doing pinning. Once we get non-pinning class init it should just show up on the vthread as expected. ------------- PR Comment: https://git.openjdk.org/jdk/pull/25367#issuecomment-2900968461
