/* * Copyright (c) 1998, 2022, Oracle and/or its affiliates. All rights reserved. * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER. * * This code is free software; you can redistribute it and/or modify it * under the terms of the GNU General Public License version 2 only, as * published by the Free Software Foundation. * * This code is distributed in the hope that it will be useful, but WITHOUT * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or * FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License * version 2 for more details (a copy is included in the LICENSE file that * accompanied this code). * * You should have received a copy of the GNU General Public License version * 2 along with this work; if not, write to the Free Software Foundation, * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. * * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA * or visit www.oracle.com if you need additional information or have any * questions. *
*/
// ObjectWaiter serves as a "proxy" or surrogate thread. // TODO-FIXME: Eliminate ObjectWaiter and use the thread-specific // ParkEvent instead. Beware, however, that the JVMTI code // knows about ObjectWaiters, so we'll have to reconcile that code. // See next_waiter(), first_waiter(), etc.
// The ObjectMonitor class implements the heavyweight version of a // JavaMonitor. The lightweight BasicLock/stack lock version has been // inflated into an ObjectMonitor. This inflation is typically due to // contention or use of Object.wait(). // // WARNING: This is a very sensitive and fragile class. DO NOT make any // changes unless you are fully aware of the underlying semantics. // // ObjectMonitor Layout Overview/Highlights/Restrictions: // // - The _header field must be at offset 0 because the displaced header // from markWord is stored there. We do not want markWord.hpp to include // ObjectMonitor.hpp to avoid exposing ObjectMonitor everywhere. This // means that ObjectMonitor cannot inherit from any other class nor can // it use any virtual member functions. This restriction is critical to // the proper functioning of the VM. // - The _header and _owner fields should be separated by enough space // to avoid false sharing due to parallel access by different threads. // This is an advisory recommendation. // - The general layout of the fields in ObjectMonitor is: // _header // <lightly_used_fields> // <optional padding> // _owner // <remaining_fields> // - The VM assumes write ordering and machine word alignment with // respect to the _owner field and the <remaining_fields> that can // be read in parallel by other threads. // - Generally fields that are accessed closely together in time should // be placed proximally in space to promote data cache locality. That // is, temporal locality should condition spatial locality. // - We have to balance avoiding false sharing with excessive invalidation // from coherence traffic. As such, we try to cluster fields that tend // to be _written_ at approximately the same time onto the same data // cache line. // - We also have to balance the natural tension between minimizing // single threaded capacity misses with excessive multi-threaded // coherency misses. There is no single optimal layout for both // single-threaded and multi-threaded environments. // // - See TEST_VM(ObjectMonitor, sanity) gtest for how critical restrictions are // enforced. // - Adjacent ObjectMonitors should be separated by enough space to avoid // false sharing. This is handled by the ObjectMonitor allocation code // in synchronizer.cpp. Also see TEST_VM(SynchronizerTest, sanity) gtest. // // Futures notes: // - Separating _owner from the <remaining_fields> by enough space to // avoid false sharing might be profitable. Given // http://blogs.oracle.com/dave/entry/cas_and_cache_trivia_invalidate // we know that the CAS in monitorenter will invalidate the line // underlying _owner. We want to avoid an L1 data cache miss on that // same line for monitorexit. Putting these <remaining_fields>: // _recursions, _EntryList, _cxq, and _succ, all of which may be // fetched in the inflated unlock path, on a different cache line // would make them immune to CAS-based invalidation from the _owner // field. // // - The _recursions field should be of type int, or int32_t but not // intptr_t. There's no reason to use a 64-bit type for this field // in a 64-bit JVM.
#ifndef OM_CACHE_LINE_SIZE // Use DEFAULT_CACHE_LINE_SIZE if not already specified for // the current build platform. #define OM_CACHE_LINE_SIZE DEFAULT_CACHE_LINE_SIZE #endif
class ObjectMonitor : public CHeapObj<mtObjectMonitor> { friendclass ObjectSynchronizer; friendclass ObjectWaiter; friendclass VMStructs;
JVMCI_ONLY(friendclass JVMCIVMStructs;)
static OopStorage* _oop_storage;
// The sync code expects the header field to be at offset zero (0). // Enforced by the assert() in header_addr(). volatile markWord _header; // displaced object header word - mark
WeakHandle _object; // backward object pointer // Separate _header and _owner on different cache lines since both can // have busy multi-threaded access. _header and _object are set at initial // inflation. The _object does not change, so it is a good choice to share // its cache line with _header.
DEFINE_PAD_MINUS_SIZE(0, OM_CACHE_LINE_SIZE, sizeof(volatile markWord) + sizeof(WeakHandle)); // Used by async deflation as a marker in the _owner field: #define DEFLATER_MARKER reinterpret_cast<void*>(-1) void* volatile _owner; // pointer to owning thread OR BasicLock volatile uint64_t _previous_owner_tid; // thread id of the previous owner of the monitor // Separate _owner and _next_om on different cache lines since // both can have busy multi-threaded access. _previous_owner_tid is only // changed by ObjectMonitor::exit() so it is a good choice to share the // cache line with _owner.
DEFINE_PAD_MINUS_SIZE(1, OM_CACHE_LINE_SIZE, sizeof(void* volatile) + sizeof(volatile uint64_t));
ObjectMonitor* _next_om; // Next ObjectMonitor* linkage volatile intx _recursions; // recursion count, 0 for first entry
ObjectWaiter* volatile _EntryList; // Threads blocked on entry or reentry. // The list is actually composed of WaitNodes, // acting as proxies for Threads.
ObjectWaiter* volatile _cxq; // LL of recently-arrived threads blocked on entry.
JavaThread* volatile _succ; // Heir presumptive thread - used for futile wakeup throttling
JavaThread* volatile _Responsible;
volatileint _Spinner; // for exit->spinner handoff optimization volatileint _SpinDuration;
int _contentions; // Number of active contentions in enter(). It is used by is_busy() // along with other fields to determine if an ObjectMonitor can be // deflated. It is also used by the async deflation protocol. See // ObjectMonitor::deflate_monitor(). protected:
ObjectWaiter* volatile _WaitSet; // LL of threads wait()ing on the monitor volatileint _waiters; // number of waiting threads private: volatileint _WaitSetLock; // protects Wait Queue - simple spinlock
public: staticvoid Initialize();
// Only perform a PerfData operation if the PerfData object has been // allocated and if the PerfDataManager has not freed the PerfData // objects which can happen at normal VM shutdown. // #define OM_PERFDATA_OP(f, op_str) \ do { \ if (ObjectMonitor::_sync_ ## f != NULL && \
PerfDataManager::has_PerfData()) { \
ObjectMonitor::_sync_ ## f->op_str; \
} \
} while (0)
// TODO-FIXME: the "offset" routines should return a type of off_t instead of int ... // ByteSize would also be an appropriate type. staticint owner_offset_in_bytes() { return offset_of(ObjectMonitor, _owner); } staticint recursions_offset_in_bytes() { return offset_of(ObjectMonitor, _recursions); } staticint cxq_offset_in_bytes() { return offset_of(ObjectMonitor, _cxq); } staticint succ_offset_in_bytes() { return offset_of(ObjectMonitor, _succ); } staticint EntryList_offset_in_bytes() { return offset_of(ObjectMonitor, _EntryList); }
// ObjectMonitor references can be ORed with markWord::monitor_value // as part of the ObjectMonitor tagging mechanism. When we combine an // ObjectMonitor reference with an offset, we need to remove the tag // value in order to generate the proper address. // // We can either adjust the ObjectMonitor reference and then add the // offset or we can adjust the offset that is added to the ObjectMonitor // reference. The latter avoids an AGI (Address Generation Interlock) // stall so the helper macro adjusts the offset value that is returned // to the ObjectMonitor reference manipulation code: // #define OM_OFFSET_NO_MONITOR_VALUE_TAG(f) \
((ObjectMonitor::f ## _offset_in_bytes()) - markWord::monitor_value)
// Returns true if this OM has an owner, false otherwise. bool has_owner() const; void* owner() const; // Returns NULL if DEFLATER_MARKER is observed. void* owner_raw() const; // Returns true if owner field == DEFLATER_MARKER and false otherwise. bool owner_is_DEFLATER_MARKER() const; // Returns true if 'this' is being async deflated and false otherwise. bool is_being_async_deflated(); // Clear _owner field; current value must match old_value. void release_clear_owner(void* old_value); // Simply set _owner field to new_value; current value must match old_value. void set_owner_from(void* old_value, void* new_value); // Simply set _owner field to current; current value must match basic_lock_p. void set_owner_from_BasicLock(void* basic_lock_p, JavaThread* current); // Try to set _owner field to new_value if the current value matches // old_value, using Atomic::cmpxchg(). Otherwise, does not change the // _owner field. Returns the prior value of the _owner field. void* try_set_owner_from(void* old_value, void* new_value);
// Simply get _next_om field.
ObjectMonitor* next_om() const; // Simply set _next_om field to new_value. void set_next_om(ObjectMonitor* new_value);
// Returns true if the specified thread owns the ObjectMonitor. Otherwise // returns false and throws IllegalMonitorStateException (IMSE). bool check_owner(TRAPS);
Die Informationen auf dieser Webseite wurden
nach bestem Wissen sorgfältig zusammengestellt. Es wird jedoch weder Vollständigkeit, noch Richtigkeit,
noch Qualität der bereit gestellten Informationen zugesichert.
Bemerkung:
Die farbliche Syntaxdarstellung ist noch experimentell.