Hello Ciro,
I checked the configs/example/se.py and configs/common/Options.py.
In se.py
"parser = optparse.OptionParser()
Options.addCommonOptions(parser)
Options.addSEOptions(parser)
(options, args) = parser.parse_args()"
in Options.py
" def addSEOptions(parser):
parser.add_option("-c", "--cmd", default="", help="The binary
to run in syscall emulation mode.")
"
we add cmd parameter"/home/borg39/test/test" into configuration script"
configs/example/se.py", so I think now addSEOptions(parser) is changed
"parser.add_option("-c", "--cmd", default="/home/borg39/test/test",
help="The binary to run in syscall emulation mode.")". I am not sure if my
understanding is right or not. And if it is right, then how can I get the
default="/home/borg39/test/test"?
With best regards
Yunxia Zhu
On Mon, 17 Dec 2018 at 16:02, Ciro Santilli <[email protected]> wrote:
> On 12/17/18 1:11 PM, Yunxia Zhu wrote:
> > Hello everyone,
> >
> > I want to clarify my question in detail.
> >
> > Here it is my script:
> > build/X86/gem5.opt \
> > configs/example/se.py \
> > -c /home/borg39/test/test \
> >
> > When I run it in gem5 SE mode, it can work well and load the binary file
> > "test". But I don't know the interface of the script and gem5. How does
> > gem5 know where to get these parameters? Does anyone have the same
> problem?
> >
>
> To pass CLI parameters to the se.py program, use --option. Mentioned at:
> http://gem5.org/Running_gem5#Script_Options
>
> Always try to se.py --help | less to search for new options.
>
> >
> > with best regards
> > Yunxia Zhu
> >
> > _______________________________________________
> > gem5-users mailing list
> > [email protected]
> > http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
> >
>
>
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
