Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of weldonwjw@gmail.com designates
 64.233.182.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type;
        b=PzoSwDF8Ig939XGaMleVr8eoRjcMwi+Q0gmgh/A+d9GCPGpBIz7eVTdbKCnSOs5RsjDQtwpHk7hnGrqZ4XPxlA1tkKvl7YfL3YMTfPaH8hXoPvZ/nTMZd5ajkj99Bi42uobSSA4eT6Ho4iY6p2AhJU4R7ncdXAh9bZ+hMrBKaTQ=
Message-ID: <4dd1f3f00703041432i39cab5bax53f3aacf0bc88d40@mail.gmail.com>
Date: Sun, 4 Mar 2007 14:32:58 -0800
From: "Weldon Washburn" <weldonwjw@gmail.com>
To: dev@harmony.apache.org
Subject: [drlvm][threading] synchronizing native and java access of the thread
 state (Harmony-3289)
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_78455_26809869.1173047578739"

------=_Part_78455_26809869.1173047578739
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I decided to put a response to H3289 on the dev list since it is a general
threading issue.  Please look at 3289 for background info.

In response to the question about JVMTI functions being able to grab a lock
in java.lang.Thread class, maybe a workable approach would be to replace
locking the java object with a mutex created in native code and stuffed into
a private int field of java.lang.Thread.  The Java code would use  native
method APIs to grab and release this new native mutex.   And the native code
(including JVMTI) would use the standard hymutex_lock(), hymutex_unlock().
The native code would manage the life-cycle of the private int field
containing a pointer to the native mutex.


-- 
Weldon Washburn
Intel Enterprise Solutions Software Division

------=_Part_78455_26809869.1173047578739--