Mailing-List: contact commits-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Message-ID: <25680128.1193029730626.JavaMail.jira@brutus>
Date: Sun, 21 Oct 2007 22:08:50 -0700 (PDT)
From: "weldon washburn (JIRA)" <jira@apache.org>
To: commits@harmony.apache.org
Subject: [jira] Updated: (HARMONY-4937) [drlvm][thread]
 suspend_enable()/suspend_disable() race condition detector
In-Reply-To: <12486346.1192191230602.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HARMONY-4937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

weldon washburn updated HARMONY-4937:
-------------------------------------

    Attachment: test_native_exp_sync.c

I updated the test kernel.  It turns out that the java thread suspend/resume test was wrong.  I also commented out some #define macros for now.  I found them confusing.  We can put the back once the basic algorithm is working OK.

> [drlvm][thread] suspend_enable()/suspend_disable() race condition detector
> --------------------------------------------------------------------------
>
>                 Key: HARMONY-4937
>                 URL: https://issues.apache.org/jira/browse/HARMONY-4937
>             Project: Harmony
>          Issue Type: Sub-task
>          Components: DRLVM
>            Reporter: Pavel Rebriy
>         Attachments: H4937_test.patch, test_native_exp_sync.c
>
>
> This is an experimental issue. Its goal is to define race condition in present suspend_disable/suspend_enable mechanism and to develop a new one.
> The issue is implemented as cunit test which based on DRLVM. Test works in the following way:
> Main thread (see function test_exp_sync()) starts 1 tested thread (see function test_thread_proc()), several GC requester threads (see function test_gc_request_thread_proc()) and several JAVA requester threads (see function test_java_request_thread_proc()). Tested thread makes suspend_disable()/suspend_enable() in a loop. Requester threads ask GC or JAVA suspend()/resume() tested thread properly. Main thread controls the execution.
> By default test is base on hythread functionality. If define TESTED_RUN is changed to 1, tested functionality will be used. Tested functionality is base on algorithm which describes in HARMONY-4908.
> To check the test need to complete the following steps:
> 1. Apply the patch:
>      $ cd <harmony>/working_vm
>      $ patch -p1 -i test.patch
> 2. Build DRLVM:
>      $ cd build
>      $ ./build.bat
> 3. Build and run cunit test:
>      $ ./build.bat cunit.test
> The result of running will be in <harmony>/working_vm/build/win_ia32_msvc_debug/tests/cunit.tests/results.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.