I'm actually not familiar with the checkpoint_after.c program so I'm not sure I can help with that specific problem. I usually just call the ptlcall to make a checkpoint inside of my program or use the parsec with hooks which will make checkpoints at the start of an ROI.
On Wed, May 15, 2013 at 7:45 PM, NA NA <[email protected]> wrote: > Dear Paul Rosenfield, > > When I tried: "vinagre localhost:5900", it said that qemu is disconnected, > meaning the machine isn't setup correctly? > > Also another question, when I first created a checkpoint > checkpoint_after.c inside the ubuntu-natty.qcow2 image, how did it know > that I wanted to run the ./FFT program? Also to make the simulation stop, I > need to apply -stopinsns right? For example the first checkpoint is at > 100000, if-stopinsns is 100000, then theoretically the program had run > 100000 instructions and stopped? > > Thank you very much for your help! > > Thanks, > > Max H. Lei > > > ------------------------------ > Date: Wed, 15 May 2013 19:34:58 -0400 > > Subject: Re: [marss86-devel] Run_Bench.py > From: [email protected] > To: [email protected] > CC: [email protected] > > To reply to the thread, just make sure that > [email protected] is CC'd. > > The default behavior of run_bench.py is to use VNC mode so I'm not sure if > you'll see any output on the console. Try to connect via vnc to > localhost:5900 to see if you can see the machine running. > > > > On Wed, May 15, 2013 at 7:31 PM, NA NA <[email protected]> wrote: > > Dear Paul Rosenfield, > > Hi, I finally got it working, but I was stuck in char device redirected to > /dev/pts/7, is there something wrong with the configuration file? > > Also do you know how to reply to the thread directly? > > Thanks, > > Max H. Lei > > ------------------------------ > Date: Wed, 15 May 2013 17:10:11 -0400 > Subject: Re: [marss86-devel] Run_Bench.py > From: [email protected] > To: [email protected] > CC: [email protected] > > > You need to specify an output directory to the python script as a command > line argument (-d if I'm not mistaken, but run ./run_bench.py --help for a > list of them). > > > On Wed, May 15, 2013 at 5:45 AM, Max <[email protected]> wrote: > > Hi All, > > I'm trying to run the run_bench.py script, and I had created a checkpoint > in > the ubuntu-natty.qcow2 by using the checkpoint_after.c (compiled at Ubuntu > host, and transferred to qemu guest OS by scp). > > This is my configuration file: > > [DEFAULT] > marss_dir = /home/max/marrs > util_dir = /home/max/marss/util > img_dir = /home/max/DiskImage > qemu_bin = /home/max/marss/qemu/qemu-system-x86_64 > default_simconfig = -kill-after-run -quiet > > [suite FFT] > checkpoints = First > > [run FFT] > suite = FFT > images = /home/max/DiskImage/ubuntu-natty.qcow2 > memory = 2G > simconfig = -logfile %(out_dir)s/%(bench)s.log > -stats %(out_dir)s/%(bench)s.yml > -machine atom_single_core > %(default_simconfig)s > > The "first" is a checkpoint at user instruction after 1000, and named first > created by the checkpoint_after.c > > When I ran the ./run_bench.py, I'm getting a strange error: > > Traceback (most recent call last): > File "./util/run_bench.py", line 224, in <module> > run_configs.extend(get_run_configs(arg, options, conf_parser)) > File "./util/run_bench.py", line 151, in get_run_configs > output_dir = options.output_dir + "/" > TypeError: unsupported operand type(s) for +: 'NoneType' and 'str' > > Has anyone met this problem before? > > By the way, when I run checkpoint_after, it crashes Qemu, but when I get > into Qemu again, the checkpoint_after turned green letters (it was white > before I called chmod and sudo to run the compiled program). Is this a > normal behavior? > > Thanks all for your help, it might be a very stupid question, but I'm very > inexperienced with python and Linux. > > Thanks again for your help! > > > > _______________________________________________ > http://www.marss86.org > Marss86-Devel mailing list > [email protected] > https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel > > > >
_______________________________________________ http://www.marss86.org Marss86-Devel mailing list [email protected] https://www.cs.binghamton.edu/mailman/listinfo/marss86-devel
