when you pass the variable HELLO via -ETEST to m5, all you're doing is essentially flipping a switch so that, as you say, Benchmarks.py knows to set a pointer to hello.rcS. this rcS file is not on the disk image. if you look in Benchmarks.py, it is pointing to an rcS file external to the disk image. see Configs.py for what doing "script(*.rcS)" actually does.
it is up to you to write this rcS file, and it will act like any other rcS file and execute whatever you tell it, including running your hello benchmark. you can see examples in m5/configs/boot.
what we normally do is put all the files in boot in a common directory somewhere, and then in configs/fullsys/Configs.py, set the appropriate BOOTDIR parameter to point to the right directory to run any rcS file we choose.
Lisa
On 12/7/05, Mario Donato Marino <[EMAIL PROTECTED]> wrote:
Hi,
Suppose I put my application on benchmarks/hello inside the
image.
Supose I want to run just a simple test:
ALPHA_FS/m5.debug -d output -ETEST=HELLO ../configs/fullsys/run.py
From what I read the -ETEST is passed to m5, and specificaly this
environment variable is passed to configs/fullsys/Benchmarks.py.
From what I have understood, if I want to include my benchmark, it´s just
needed to include it in configs/fullsys/Benchmarks.py the pointer to
hello.rcS. So, the HELLO variable is passed.
I would like to understand how this variable is passed to /etc/init.d/rcS
and how it can specify the benchmark (hello.rcS, etc) you want to run if
you have several ones.
Thanks for your help,
Mario
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&opÌk
_______________________________________________
m5sim-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/m5sim-users
