RFR: 8265933: Move Java monitor related fields from class Thread to JavaThread
Coleen Phillimore
coleenp at openjdk.java.net
Wed Apr 28 20:58:57 UTC 2021
On Tue, 27 Apr 2021 18:08:19 GMT, Patricio Chilano Mateo <pchilanomate at openjdk.org> wrote:
> Hi,
>
> Please review the following change. Fields in class Thread related to Java object monitors like _current_pending_monitor, _current_pending_monitor_is_from_java, _current_waiting_monitor and _Stalled should be moved to the JavaThread class. Members _OnTrap and _TypeTag were grouped together with _Stalled but are not used so I removed them. It seems they were part of the ObjectMonitor implementation at some point but I couldn't find how they were used.
> Tested in mach5 tier1-2.
>
> Thanks,
> Patricio
Marked as reviewed by coleenp (Reviewer).
src/hotspot/share/runtime/thread.hpp line 666:
> 664:
> 665: public:
> 666: ParkEvent * volatile _ParkEvent; // for Object monitors, JVMTI raw monitors,
So are jvmti raw monitors not required to be taken on a Java Thread?
-------------
PR: https://git.openjdk.java.net/jdk/pull/3722
More information about the hotspot-runtime-dev
mailing list