Re: [Gems-users] Strange behavior (BARRIER_CYCLE = 0) collected of vacation on LogTM-SE


Date: Sun, 25 Oct 2009 12:14:24 -0500
From: Polina Dudnik <pdudnik@xxxxxxxxx>
Subject: Re: [Gems-users] Strange behavior (BARRIER_CYCLE = 0) collected of vacation on LogTM-SE
Ruzhu,

Did you turn on all the debugging? Do you see the message that indicates that a thread entered the barrier? Because my bet would be that either you are not running multithreaded or vacation never goes down the path that has the barrier. 

Here's something that could help you debug: define some magic calls that just print a message and place them in vacation to see where it is and what it is doing. So, right in the barrier function, just put in the magic call that prints out how many threads are in the barrier by now. That will let you see whether or not barrier is ever invoked and how many threads are in the barrier. Don't put in printf, that won't work as well because the print doesn't make it to the terminal immediately whereas the magic call will print immediately.

Polina

On Sun, Oct 25, 2009 at 4:06 AM, ruzhu kao <kaoruzhu@xxxxxxxxx> wrote:
Hi all:
    Recently I have modified STAMP-9.10 to make them run on LogTM-SE
(Simics 2.2.19 + GEMS 2.1). I test these binaries and collect some
stats file, all of them show me reasonable profile files except
vacation that its BARRIER_BREAKDOWN_CYCLE is zero which indicates
there must some mistakes on my modifications. However I use the same
lib to compile these applications and the execute them on the same
environment. I check the workload setup, and I believe I have obeyed
the rules on WISC' wiki. This problem drives me crazy. Have you ever
met this problem? If so, how to solve this problem.
  Another question is about cache warming up, I have test bayes
running on my checkpoint without cache warming up, it can generate
stats file so I assume both the magic breakpoints are set correctly.
Then I make a warm up checkpoint, when I run the same bayes, it can
load ruby but without out stats file even after it printed the output
message after the second magic breakpoint. Loading ruby which seems
the first magic breakpoint is ok, why the second magic breakpoint miss
its effecting.

 I hope you can help me out. Thanks in advance.


Sincerely yours:
Ruzhu
_______________________________________________
Gems-users mailing list
Gems-users@xxxxxxxxxxx
https://lists.cs.wisc.edu/mailman/listinfo/gems-users
Use Google to search the GEMS Users mailing list by adding "site:https://lists.cs.wisc.edu/archive/gems-users/" to your search.


[← Prev in Thread] Current Thread [Next in Thread→]