Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread [v2]

2025-05-13 Thread Viktor Klang
On Mon, 12 May 2025 14:01:16 GMT, Alan Bateman wrote: >> Data structures that are accessed by both virtual threads and their carriers >> require the virtual thread to pin the continuation to avoid potential >> deadlock. A deadlock can arise when a virtual thread is preempted, is >> selected an

Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread [v2]

2025-05-13 Thread Jaikiran Pai
On Mon, 12 May 2025 14:01:16 GMT, Alan Bateman wrote: >> Data structures that are accessed by both virtual threads and their carriers >> require the virtual thread to pin the continuation to avoid potential >> deadlock. A deadlock can arise when a virtual thread is preempted, is >> selected an

Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread [v2]

2025-05-12 Thread Alan Bateman
> Data structures that are accessed by both virtual threads and their carriers > require the virtual thread to pin the continuation to avoid potential > deadlock. A deadlock can arise when a virtual thread is preempted, is > selected and scheduled to be the next owner of the lock/resource, but c

Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread

2025-05-12 Thread Alan Bateman
On Mon, 12 May 2025 09:01:34 GMT, Jaikiran Pai wrote: >> Data structures that are accessed by both virtual threads and their carriers >> require the virtual thread to pin the continuation to avoid potential >> deadlock. A deadlock can arise when a virtual thread is preempted, is >> selected an

Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread

2025-05-12 Thread Jaikiran Pai
On Wed, 26 Feb 2025 19:46:41 GMT, Alan Bateman wrote: > Data structures that are accessed by both virtual threads and their carriers > require the virtual thread to pin the continuation to avoid potential > deadlock. A deadlock can arise when a virtual thread is preempted, is > selected and sc

RFR: 8350765: Need to pin when accessing thread container from virtual thread

2025-05-12 Thread Alan Bateman
Data structures that are accessed by both virtual threads and their carriers require the virtual thread to pin the continuation to avoid potential deadlock. A deadlock can arise when a virtual thread is preempted, is selected and scheduled to be the next owner of the lock/resource, but can't exe

Re: RFR: 8350765: Need to pin when accessing thread container from virtual thread

2025-05-12 Thread Viktor Klang
On Wed, 26 Feb 2025 19:46:41 GMT, Alan Bateman wrote: > Data structures that are accessed by both virtual threads and their carriers > require the virtual thread to pin the continuation to avoid potential > deadlock. A deadlock can arise when a virtual thread is preempted, is > selected and sc