You can just run SE mode by building the common .opt file and then using:
./build/X86/gem5.opt ./configs/example/se.py.

The se.py file also has been modified to support the change in the binary
file..

Pritha

On Sat, Feb 18, 2012 at 11:48 PM, Mahmood Naderan <[email protected]>wrote:

> >there is a variable set which calls the full system mode or
> >the Syscall Emulation mode.
>
> What is that then? How can I run simulation in X86_SE?
>
> On 2/18/12, Pritha Ghoshal <[email protected]> wrote:
> > Hi Mehmood,
> >
> > You have to just run this command:
> > scons build/X86/m5.debug
> >
> > The FS and SE modes have become run time usages rather than build time.
> > Therefore the binary stays the same for both of them, whereas in the
> fs.py
> > file or se.py file there is a variable set which calls the full system
> mode
> > or the Syscall Emulation mode.
> >
> > Pritha
> >
> >
> > On Sat, Feb 18, 2012 at 12:36 PM, Mahmood Naderan
> > <[email protected]>wrote:
> >
> >> Hi
> >> It seems that variables in build_opt are changed in new revisions.
> >>
> >> for this command:
> >> scons build/X86_SE/m5.debug
> >>
> >> I get this error:
> >> Error: cannot find variables file
> >> /home/mahmood/gem5-ef8630054b5e/build/variables/X86_SE or default
> >> file(s) /home/mahmood/gem5-ef8630054b5e/build_opts/X86_SE
> >>
> >> comparing  with previous revisions, there is no X86_SE file. Instead
> >> there is only a file named  "x86".
> >>
> >> http://repo.m5sim.org/gem5/file/ef8630054b5e/build_opts
> >>
> >> --
> >> // Naderan *Mahmood;
> >> _______________________________________________
> >> gem5-users mailing list
> >> [email protected]
> >> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
> >>
> >
>
>
> --
> --
> // Naderan *Mahmood;
> _______________________________________________
> 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

Reply via email to