harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Rebriy (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-4937) [drlvm][thread] suspend_enable()/suspend_disable() race condition detector
Date Fri, 12 Oct 2007 12:36:51 GMT

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

Pavel Rebriy commented on HARMONY-4937:

The results on revision 584059:

1) On laptop.
     1.1) Present suspend mechanism: works fine
     1.2) Tested suspend mechanism (from H-4908): hangs.

2) On 1 processor with HT server.
     2.1) Present suspend mechanism: sometime test hangs, sometimes test failed due to fake
access to heap and sometimes test works fine.
     2.2) Tested suspend mechanism (from H-4908): sometime test  hangs and sometimes test
failed due to fake access to heap.

3) On 2 processor with HT server.
     3.1), 3.2) Both cases test  failed due to  fake access to heap.

> [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
> 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
> 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.

View raw message