[gem5-users] Reading the size of X86 register

2018-06-05 Thread Tariq Azmy
Hi,

Is there a way to access the data size of operand/destination register of
some instruction? For example, in mediaOpReg, there are uint8_t srcSize, as
well as uint8_t destSize but I believe these information don't get passed
to the super class, i.e. StaticInst, when it get constructed. Therefore I
couldn't access these info through staticInstPtr.

Thanks
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Compilation error

2018-06-05 Thread Mao Ye
Hi Ciro,

It is solved already. I found out the problem resides in one of the header
files I added in .
I use the latest gem5 version, on ubuntu 16.04.

Thanks!
Mao






On Tue, Jun 5, 2018 at 4:28 AM, Ciro Santilli 
wrote:

> Does it happen on a full clean build? What is your gem5 git revision?
> What is your OS? What is your compiler version? :-)
>
> On Mon, Jun 4, 2018 at 9:44 PM, Mao Ye  wrote:
> > Hi all,
> >
> > I have been using gem5 for a while without any problem. But today I met a
> > problem with my new modification and it failed at compilation stage.
> > However, I diff the following file with the one under another directory
> of
> > mine, showing no difference at all. So what might be the reason causing
> so
> > many errors?  Any suggestion will be appreciated.
> >
> > The error message is as below :
> >
> > [VER TAGS]  -> X86/sim/tags.cc
> > [ CXX] X86/python/_m5/param_DRAMCtrl.cc -> .o
> > build/X86/python/_m5/param_DRAMCtrl.cc:53:1: error: expected
> unqualified-id
> > before 'namespace'
> >  namespace py = pybind11;
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:56:13: error: 'py' has not been
> > declared
> >  module_init(py::module _internal)
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:56:24: error: expected ',' or
> '...'
> > before '&' token
> >  module_init(py::module _internal)
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected
> identifier
> > before string constant
> >  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init,
> "AbstractMemory");
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected ',' or
> '...'
> > before string constant
> > build/X86/python/_m5/param_DRAMCtrl.cc:137:75: error: expected '}' at
> end of
> > input
> >  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init,
> "AbstractMemory");
> >
>   ^
> > build/X86/python/_m5/param_DRAMCtrl.cc: In static member function
> 'static
> > void FECache::module_init(int)':
> > build/X86/python/_m5/param_DRAMCtrl.cc:58:5: error: 'py' has not been
> > declared
> >  py::module m = m_internal.def_submodule("param_DRAMCtrl");
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:5: error: 'py' has not been
> > declared
> >  py::class_ > std::unique_ptr>(m, "
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:30: error: expected
> > primary-expression before ',' token
> >  py::class_ > std::unique_ptr>(m, "
> >   ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:52: error: expected
> > primary-expression before ',' token
> >  py::class_ > std::unique_ptr>(m, "
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:86: error: 'py' was not
> declared
> > in this scope
> >  py::class_ > std::unique_ptr>(m, "
> >
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:98: error: template argument
> 2 is
> > invalid
> >  py::class_ > std::unique_ptr>(m, "DRAM
> >
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:101: error: 'm' was not
> declared
> > in this scope
> >  :class_ > std::unique_ptr>(m, "DRAMCtr
> >
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:60:14: error: 'py' is not a
> class,
> > namespace, or enumeration
> >  .def(py::init<>())
> >   ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:60:23: error: expected
> > primary-expression before '>' token
> >  .def(py::init<>())
> >^
> > build/X86/python/_m5/param_DRAMCtrl.cc:60:25: error: expected
> > primary-expression before ')' token
> >  .def(py::init<>())
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:5: error: 'py' is not a
> class,
> > namespace, or enumeration
> >  py::class_ > py::nodelete>>(m, "DRAMCtrl")
> >  ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:24: error: expected
> > primary-expression before ',' token
> >  py::class_ > py::nodelete>>(m, "DRAMCtrl")
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:40: error: expected
> > primary-expression before ',' token
> >  py::class_ > py::nodelete>>(m, "DRAMCtrl")
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:68: error: the value of 'py'
> is
> > not usable in a constant expression
> >  py::class_ > py::nodelete>>(m, "DRAMCtrl")
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:59:86: note: 'py' was not
> declared
> > 'constexpr'
> >  py::class_ > std::unique_ptr>(m, "
> >
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:80: error: type/value
> mismatch at
> > argument 2 in template parameter list for 'template
> > class std::unique_ptr'
> >  py::class_ > py::nodelete>>(m, "DRAMCtrl")
> >
> > ^
> > build/X86/python/_m5/param_DRAMCtrl.cc:132:80: note:   expected a type,
> got
> > 'py'
> > 

Re: [gem5-users] Compilation error

2018-06-05 Thread Mao Ye
Hi Oscar,

I think it is because of in one of the header files I had the issue as you
described. It is solved already. Thanks!

Mao

On Tue, Jun 5, 2018 at 4:57 AM, Oscar Rosell 
wrote:

> Hi,
>
> Most (if not all) of the errors are just a consequence of the first one so
> they don't really matter. Most probably, you're missing a ";" somewhere
> before the "namespace py = pybind11;" line.
>
> Regards,
>
> Oscar
>
> On 04/06/18 22:44, Mao Ye wrote:
>
> Hi all,
>
> I have been using gem5 for a while without any problem. But today I met a
> problem with my new modification and it failed at compilation stage.
> However, I diff the following file with the one under another directory of
> mine, showing no difference at all. So what might be the reason causing so
> many errors?  Any suggestion will be appreciated.
>
> The error message is as below :
>
> [VER TAGS]  -> X86/sim/tags.cc
> [ CXX] X86/python/_m5/param_DRAMCtrl.cc -> .o
> build/X86/python/_m5/param_DRAMCtrl.cc:53:1: error: expected
> unqualified-id before 'namespace'
>  namespace py = pybind11;
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:56:13: error: 'py' has not been
> declared
>  module_init(py::module _internal)
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:56:24: error: expected ',' or
> '...' before '&' token
>  module_init(py::module _internal)
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected identifier
> before string constant
>  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init,
> "AbstractMemory");
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected ',' or
> '...' before string constant
> build/X86/python/_m5/param_DRAMCtrl.cc:137:75: error: expected '}' at end
> of input
>  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init,
> "AbstractMemory");
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc: In static member function 'static
> void FECache::module_init(int)':
> build/X86/python/_m5/param_DRAMCtrl.cc:58:5: error: 'py' has not been
> declared
>  py::module m = m_internal.def_submodule("param_DRAMCtrl");
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:5: error: 'py' has not been
> declared
>  py::class_ std::unique_ptr>(m, "
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:30: error: expected
> primary-expression before ',' token
>  py::class_ std::unique_ptr>(m, "
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:52: error: expected
> primary-expression before ',' token
>  py::class_ std::unique_ptr>(m, "
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:86: error: 'py' was not
> declared in this scope
>  py::class_ std::unique_ptr>(m, "
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:98: error: template argument 2
> is invalid
>  py::class_ std::unique_ptr>(m, "DRAM
>
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:101: error: 'm' was not
> declared in this scope
>  :class_ std::unique_ptr>(m, "DRAMCtr
>
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:14: error: 'py' is not a class,
> namespace, or enumeration
>  .def(py::init<>())
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:23: error: expected
> primary-expression before '>' token
>  .def(py::init<>())
>^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:25: error: expected
> primary-expression before ')' token
>  .def(py::init<>())
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:5: error: 'py' is not a class,
> namespace, or enumeration
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:24: error: expected
> primary-expression before ',' token
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:40: error: expected
> primary-expression before ',' token
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:68: error: the value of 'py'
> is not usable in a constant expression
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:86: note: 'py' was not declared
> 'constexpr'
>  py::class_ std::unique_ptr>(m, "
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:80: error: type/value mismatch
> at argument 2 in template parameter list for 'template _Dp> class std::unique_ptr'
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:80: note:   expected a type,
> got 'py'
> build/X86/python/_m5/param_DRAMCtrl.cc: At global scope:
> build/X86/python/_m5/param_DRAMCtrl.cc:135:1: error: expected
> unqualified-id at end of input
>  };
>  ^
> scons: *** 

Re: [gem5-users] Multi-core execution - gem5 & big.LITTLE total cores

2018-06-05 Thread Ciro Santilli
On Tue, Jun 5, 2018 at 3:21 PM, Georgios S. Bousdras
 wrote:
> Dear all,
>
> I wonder if It is possible to run the gem5 on a multi-core mode(like the
> scons build/ARM/gem5.opt -j “n”) in order to reduce the simulation time.
>

No: https://github.com/cirosantilli-work/gem5-issues/issues/15

> In addition, what is the difference between armv8_gem5_v1_big_little_2_2.dtb
> and armv8_gem5_v1_big_little_2_4.dtb?
> I ask because I want to simulate a 8 core big.LITTLE system of 4 big cores
> and 4 little cores and I don’t know which is a suitable .dtb file.
>

Observe the contents of dtbs as explained at:
https://stackoverflow.com/questions/14000736/tool-to-visualize-the-device-tree-file-dtb-used-by-the-linux-kernel/39931834#39931834

This shows that 2_4 means 2 little and 4 big and won't work.

For 4x4, you need to either:

- convert to dts, modify it manually, reconvert to dtb
- modify the in tree dts used to generate the dtb and run make again
- fs_bigLITTLE.py has an automatic dtb generation if you don't use the
--dtb flag, it should in theory work. Have a look at the script
source.

> Best Regards,
> George
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

[gem5-users] Multi-core execution - gem5 & big.LITTLE total cores

2018-06-05 Thread Georgios S. Bousdras
Dear all, 

I wonder if It is possible to run the gem5 on a multi-core mode(like the scons 
build/ARM/gem5.opt -j “n”) in order to reduce the simulation time. 

In addition, what is the difference between armv8_gem5_v1_big_little_2_2.dtb 
and armv8_gem5_v1_big_little_2_4.dtb?
I ask because I want to simulate a 8 core big.LITTLE system of 4 big cores and 
4 little cores and I don’t know which is a suitable .dtb file. 

Best Regards,
George___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Compilation error

2018-06-05 Thread Oscar Rosell

Hi,

Most (if not all) of the errors are just a consequence of the first one 
so they don't really matter. Most probably, you're missing a ";" 
somewhere before the "namespace py = pybind11;" line.


Regards,

    Oscar


On 04/06/18 22:44, Mao Ye wrote:

Hi all,

I have been using gem5 for a while without any problem. But today I 
met a problem with my new modification and it failed at compilation 
stage. However, I diff the following file with the one under another 
directory of mine, showing no difference at all. So what might be the 
reason causing so many errors? Any suggestion will be appreciated.


The error message is as below :

[VER TAGS]  -> X86/sim/tags.cc
[ CXX] X86/python/_m5/param_DRAMCtrl.cc -> .o
build/X86/python/_m5/param_DRAMCtrl.cc:53:1: error: expected 
unqualified-id before 'namespace'

 namespace py = pybind11;
 ^
build/X86/python/_m5/param_DRAMCtrl.cc:56:13: error: 'py' has not been 
declared

 module_init(py::module _internal)
 ^
build/X86/python/_m5/param_DRAMCtrl.cc:56:24: error: expected ',' or 
'...' before '&' token

 module_init(py::module _internal)
    ^
build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected 
identifier before string constant
 static EmbeddedPyBind embed_obj("DRAMCtrl", module_init, 
"AbstractMemory");

   ^
build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected ',' or 
'...' before string constant
build/X86/python/_m5/param_DRAMCtrl.cc:137:75: error: expected '}' at 
end of input
 static EmbeddedPyBind embed_obj("DRAMCtrl", module_init, 
"AbstractMemory");

^
build/X86/python/_m5/param_DRAMCtrl.cc: In static member function 
'static void FECache::module_init(int)':
build/X86/python/_m5/param_DRAMCtrl.cc:58:5: error: 'py' has not been 
declared

 py::module m = m_internal.def_submodule("param_DRAMCtrl");
 ^
build/X86/python/_m5/param_DRAMCtrl.cc:59:5: error: 'py' has not been 
declared
 py::class_std::unique_ptr>(m, "

 ^
build/X86/python/_m5/param_DRAMCtrl.cc:59:30: error: expected 
primary-expression before ',' token
 py::class_std::unique_ptr>(m, "

  ^
build/X86/python/_m5/param_DRAMCtrl.cc:59:52: error: expected 
primary-expression before ',' token
 py::class_std::unique_ptr>(m, "

  ^
build/X86/python/_m5/param_DRAMCtrl.cc:59:86: error: 'py' was not 
declared in this scope
 py::class_std::unique_ptr>(m, "

^
build/X86/python/_m5/param_DRAMCtrl.cc:59:98: error: template argument 
2 is invalid
 py::class_std::unique_ptr>(m, "DRAM

^
build/X86/python/_m5/param_DRAMCtrl.cc:59:101: error: 'm' was not 
declared in this scope
 :class_std::unique_ptr>(m, "DRAMCtr

^
build/X86/python/_m5/param_DRAMCtrl.cc:60:14: error: 'py' is not a 
class, namespace, or enumeration

 .def(py::init<>())
  ^
build/X86/python/_m5/param_DRAMCtrl.cc:60:23: error: expected 
primary-expression before '>' token

 .def(py::init<>())
   ^
build/X86/python/_m5/param_DRAMCtrl.cc:60:25: error: expected 
primary-expression before ')' token

 .def(py::init<>())
 ^
build/X86/python/_m5/param_DRAMCtrl.cc:132:5: error: 'py' is not a 
class, namespace, or enumeration
 py::class_py::nodelete>>(m, "DRAMCtrl")

 ^
build/X86/python/_m5/param_DRAMCtrl.cc:132:24: error: expected 
primary-expression before ',' token
 py::class_py::nodelete>>(m, "DRAMCtrl")

    ^
build/X86/python/_m5/param_DRAMCtrl.cc:132:40: error: expected 
primary-expression before ',' token
 py::class_py::nodelete>>(m, "DRAMCtrl")

  ^
build/X86/python/_m5/param_DRAMCtrl.cc:132:68: error: the value of 
'py' is not usable in a constant expression
 py::class_py::nodelete>>(m, "DRAMCtrl")

^
build/X86/python/_m5/param_DRAMCtrl.cc:59:86: note: 'py' was not 
declared 'constexpr'
 py::class_std::unique_ptr>(m, "

^
build/X86/python/_m5/param_DRAMCtrl.cc:132:80: error: type/value 
mismatch at argument 2 in template parameter list for 'template_Tp, class _Dp> class std::unique_ptr'
 py::class_py::nodelete>>(m, "DRAMCtrl")

^
build/X86/python/_m5/param_DRAMCtrl.cc:132:80: note: expected a type, 
got 'py'

build/X86/python/_m5/param_DRAMCtrl.cc: At global scope:
build/X86/python/_m5/param_DRAMCtrl.cc:135:1: error: expected 
unqualified-id at end of input

 };
 ^
scons: *** [build/X86/python/_m5/param_DRAMCtrl.o] Error 1
scons: building terminated because of errors.


--
Mao Ye,


___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users




smime.p7s
Description: S/MIME Cryptographic Signature
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Re: [gem5-users] Error in running Moby(Asimbench) benchmark in gem5

2018-06-05 Thread 조해윤
I found what is the problem.

The cause is not a dtb file. It is --mem-size.
You need to specify the unit of the capacity (MB or GB). As I think, it is
due to the lack of memory size.

2018-06-05 17:43 GMT+09:00 조해윤 :

> Dear Mitali Sinha.
>
> Sorry for late reply.
> Try it without specified dtb file in command line.
>
> Actually, I run moby by myself again before writing the reply.
>
> ./build/ARM/gem5.opt configs/example/fs.py --machine-type=RealViewPBX
> --os-type=android-ics --kernel=/dist/m5/system/
> binaries/vmlinux.smp.ics.arm.asimbench.2.6.35
> --disk-image=/dist/m5/system/disks/ARMv7a-ICS-Android.SMP.Asimbench-v3.img
> --mem-size=256MB --script=/dist/m5/system/boot/adobe.rcS --frame-capture
>
> Although it is still booted up, there is no problem.
>
> Best Regards,
> Haeyoon Cho.
>
> 2018-06-03 22:13 GMT+09:00 Mitali Sinha :
>
>> @Haeyoon Cho sorry for late reply.
>>
>> I tried making the changes as follows:
>> gem5/configs/common/FSConfig.py:
>>  default_dtbs = {
>> "RealViewEB": None,
>> "RealViewPBX": None,
>> "VExpress_EMM": "armv7_gem5_v1_%dcpu.20170616.dtb" % num_cpus,
>> "VExpress_EMM64": "vexpress.aarch64.20140821.dtb",
>> }
>>
>> default_kernels = {
>> "RealViewEB": "vmlinux.arm.smp.fb.2.6.38.8",
>> "RealViewPBX": "vmlinux.smp.ics.arm.asimbench.2.6.35",
>> "VExpress_EMM64": "vmlinux.aarch64.20140821",
>> }
>>
>> Then, I ran the following command:
>> build/ARM/gem5.opt configs/example/fs.py --os-type=android-ics
>> --machine-type=RealView_PBX --mem-size=512 --cpu-type=MinorCPU --caches
>> --disk-image=/home/sujay/gem5/full_system_asimbench/disks/AR
>> Mv7a-ICS-Android.SMP.Asimbench-v3.img --kernel=/home/sujay/gem5/full
>> _system_asimbench/binaries/vmlinux.smp.ics.arm.asimbench.2.6.35
>> --dtb-filename=/home/sujay/gem5/full_system_asimbench/binaries/armv7_gem5_v1_1cpu.dtb
>> --script=/home/sujay/gem5/full_system_asimbench/asimbench_
>> boot_scripts/adobe.rcS
>>
>> It gives the following error:
>> --- BEGIN LIBC BACKTRACE ---
>> build/ARM/gem5.opt(_Z15print_backtracev+0x28)[0xd99e78]
>> build/ARM/gem5.opt(_Z12abortHandleri+0x46)[0xdac9f6]
>> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f5eb6c93390]
>> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f5eb569b428]
>> /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5eb569d02a]
>> build/ARM/gem5.opt[0x939dcf]
>> build/ARM/gem5.opt[0x123ff36]
>> build/ARM/gem5.opt(_ZN8DRAMCtrl4initEv+0x20)[0x12626e0]
>> build/ARM/gem5.opt[0x11c065a]
>> build/ARM/gem5.opt[0xa224b7]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra
>> meEx+0x6f55)[0x7f5eb6f4fe65]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> eEx+0x85c)[0x7f5eb708704c]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra
>> meEx+0x6ffd)[0x7f5eb6f4ff0d]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> eEx+0x85c)[0x7f5eb708704c]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra
>> meEx+0x6ffd)[0x7f5eb6f4ff0d]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> eEx+0x85c)[0x7f5eb708704c]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> e+0x19)[0x7f5eb6f48d99]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra
>> meEx+0x613b)[0x7f5eb6f4f04b]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> eEx+0x85c)[0x7f5eb708704c]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFra
>> meEx+0x6ffd)[0x7f5eb6f4ff0d]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> eEx+0x85c)[0x7f5eb708704c]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCod
>> e+0x19)[0x7f5eb6f48d99]
>> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFl
>> ags+0x76)[0x7f5eb6fc31e6]
>> build/ARM/gem5.opt(_Z6m5MainiPPc+0x8f)[0xdab3ef]
>> build/ARM/gem5.opt(main+0x33)[0x8ba673]
>> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f5eb5686830]
>> build/ARM/gem5.opt(_start+0x29)[0x8f6e19]
>> --- END LIBC BACKTRACE ---
>> Aborted (core dumped)
>>
>>
>>
>> I don't know if I am doing it correctly. Also I am not sure if I am using
>> the correct dtb files and boot_emm.arm files that I have collected from
>> http://www.gem5.org/dist/current/arm/aarch-system-20180409.tar.xz.
>> 
>> image.
>>
>> Please help.
>>
>>
>> On Tue, May 29, 2018 at 8:43 PM, 조해윤  wrote:
>>
>>> Dear Mitali Sinha.
>>>
>>> In my case, I run moby bench with RealView_PBX machine type.
>>> I don't know if it is the cause, but give it a try.
>>>
>>> Best Regard,
>>> Haeyoon Cho.
>>>
>>> 2018-05-29 20:39 GMT+09:00 Mitali Sinha :
>>>
 I have followed the instructions provided in the gem5.org website to
 run the Moby benchmarks on gem5 as follows:

 1.  Downloaded the Asimbench from https://bitbucket.org/yongbing
 _huang/asimbench/downloads/ which contains the following folders and
 files:
  1.  asimbench_android_arm_kernel 

Re: [gem5-users] Error in running Moby(Asimbench) benchmark in gem5

2018-06-05 Thread 조해윤
 Dear Mitali Sinha.

Sorry for late reply.
Try it without specified dtb file in command line.

Actually, I run moby by myself again before writing the reply.

./build/ARM/gem5.opt configs/example/fs.py --machine-type=RealViewPBX
--os-type=android-ics
--kernel=/dist/m5/system/binaries/vmlinux.smp.ics.arm.asimbench.2.6.35
--disk-image=/dist/m5/system/disks/ARMv7a-ICS-Android.SMP.Asimbench-v3.img
--mem-size=256MB --script=/dist/m5/system/boot/adobe.rcS --frame-capture

Although it is still booted up, there is no problem.

Best Regards,
Haeyoon Cho.

2018-06-03 22:13 GMT+09:00 Mitali Sinha :

> @Haeyoon Cho sorry for late reply.
>
> I tried making the changes as follows:
> gem5/configs/common/FSConfig.py:
>  default_dtbs = {
> "RealViewEB": None,
> "RealViewPBX": None,
> "VExpress_EMM": "armv7_gem5_v1_%dcpu.20170616.dtb" % num_cpus,
> "VExpress_EMM64": "vexpress.aarch64.20140821.dtb",
> }
>
> default_kernels = {
> "RealViewEB": "vmlinux.arm.smp.fb.2.6.38.8",
> "RealViewPBX": "vmlinux.smp.ics.arm.asimbench.2.6.35",
> "VExpress_EMM64": "vmlinux.aarch64.20140821",
> }
>
> Then, I ran the following command:
> build/ARM/gem5.opt configs/example/fs.py --os-type=android-ics
> --machine-type=RealView_PBX --mem-size=512 --cpu-type=MinorCPU --caches
> --disk-image=/home/sujay/gem5/full_system_asimbench/disks/
> ARMv7a-ICS-Android.SMP.Asimbench-v3.img --kernel=/home/sujay/gem5/
> full_system_asimbench/binaries/vmlinux.smp.ics.arm.asimbench.2.6.35
> --dtb-filename=/home/sujay/gem5/full_system_asimbench/
> binaries/armv7_gem5_v1_1cpu.dtb --script=/home/sujay/gem5/
> full_system_asimbench/asimbench_boot_scripts/adobe.rcS
>
> It gives the following error:
> --- BEGIN LIBC BACKTRACE ---
> build/ARM/gem5.opt(_Z15print_backtracev+0x28)[0xd99e78]
> build/ARM/gem5.opt(_Z12abortHandleri+0x46)[0xdac9f6]
> /lib/x86_64-linux-gnu/libpthread.so.0(+0x11390)[0x7f5eb6c93390]
> /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f5eb569b428]
> /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f5eb569d02a]
> build/ARM/gem5.opt[0x939dcf]
> build/ARM/gem5.opt[0x123ff36]
> build/ARM/gem5.opt(_ZN8DRAMCtrl4initEv+0x20)[0x12626e0]
> build/ARM/gem5.opt[0x11c065a]
> build/ARM/gem5.opt[0xa224b7]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6f55)[
> 0x7f5eb6f4fe65]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[
> 0x7f5eb708704c]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6ffd)[
> 0x7f5eb6f4ff0d]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[
> 0x7f5eb708704c]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6ffd)[
> 0x7f5eb6f4ff0d]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[
> 0x7f5eb708704c]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_
> EvalCode+0x19)[0x7f5eb6f48d99]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x613b)[
> 0x7f5eb6f4f04b]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[
> 0x7f5eb708704c]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x6ffd)[
> 0x7f5eb6f4ff0d]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x85c)[
> 0x7f5eb708704c]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_
> EvalCode+0x19)[0x7f5eb6f48d99]
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76)[
> 0x7f5eb6fc31e6]
> build/ARM/gem5.opt(_Z6m5MainiPPc+0x8f)[0xdab3ef]
> build/ARM/gem5.opt(main+0x33)[0x8ba673]
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f5eb5686830]
> build/ARM/gem5.opt(_start+0x29)[0x8f6e19]
> --- END LIBC BACKTRACE ---
> Aborted (core dumped)
>
>
>
> I don't know if I am doing it correctly. Also I am not sure if I am using
> the correct dtb files and boot_emm.arm files that I have collected from
> http://www.gem5.org/dist/current/arm/aarch-system-20180409.tar.xz.
> 
> image.
>
> Please help.
>
>
> On Tue, May 29, 2018 at 8:43 PM, 조해윤  wrote:
>
>> Dear Mitali Sinha.
>>
>> In my case, I run moby bench with RealView_PBX machine type.
>> I don't know if it is the cause, but give it a try.
>>
>> Best Regard,
>> Haeyoon Cho.
>>
>> 2018-05-29 20:39 GMT+09:00 Mitali Sinha :
>>
>>> I have followed the instructions provided in the gem5.org website to
>>> run the Moby benchmarks on gem5 as follows:
>>>
>>> 1.  Downloaded the Asimbench from https://bitbucket.org/yongbing
>>> _huang/asimbench/downloads/ which contains the following folders and
>>> files:
>>>  1.  asimbench_android_arm_kernel :
>>> vmlinux.smp.ics.arm.asimbench.2.6.35
>>>  2.  asimbench_boot_scripts : contains the rcs scripts for
>>> different benchmarks
>>>  3.  asimbench_disk_image :  
>>> ARMv7a-ICS-Android.SMP.Asimbench-v3.img;
>>> sdcard-1g-mxplayer.img
>>>
>>> 2.  I have used the "armv7_gem5_v1_1cpu.dtb" and "boot_emm.arm" binaries
>>> downloaded from 

Re: [gem5-users] Compilation error

2018-06-05 Thread Ciro Santilli
Does it happen on a full clean build? What is your gem5 git revision?
What is your OS? What is your compiler version? :-)

On Mon, Jun 4, 2018 at 9:44 PM, Mao Ye  wrote:
> Hi all,
>
> I have been using gem5 for a while without any problem. But today I met a
> problem with my new modification and it failed at compilation stage.
> However, I diff the following file with the one under another directory of
> mine, showing no difference at all. So what might be the reason causing so
> many errors?  Any suggestion will be appreciated.
>
> The error message is as below :
>
> [VER TAGS]  -> X86/sim/tags.cc
> [ CXX] X86/python/_m5/param_DRAMCtrl.cc -> .o
> build/X86/python/_m5/param_DRAMCtrl.cc:53:1: error: expected unqualified-id
> before 'namespace'
>  namespace py = pybind11;
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:56:13: error: 'py' has not been
> declared
>  module_init(py::module _internal)
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:56:24: error: expected ',' or '...'
> before '&' token
>  module_init(py::module _internal)
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected identifier
> before string constant
>  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init, "AbstractMemory");
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:137:33: error: expected ',' or '...'
> before string constant
> build/X86/python/_m5/param_DRAMCtrl.cc:137:75: error: expected '}' at end of
> input
>  static EmbeddedPyBind embed_obj("DRAMCtrl", module_init, "AbstractMemory");
>^
> build/X86/python/_m5/param_DRAMCtrl.cc: In static member function 'static
> void FECache::module_init(int)':
> build/X86/python/_m5/param_DRAMCtrl.cc:58:5: error: 'py' has not been
> declared
>  py::module m = m_internal.def_submodule("param_DRAMCtrl");
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:5: error: 'py' has not been
> declared
>  py::class_ std::unique_ptr>(m, "
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:30: error: expected
> primary-expression before ',' token
>  py::class_ std::unique_ptr>(m, "
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:52: error: expected
> primary-expression before ',' token
>  py::class_ std::unique_ptr>(m, "
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:86: error: 'py' was not declared
> in this scope
>  py::class_ std::unique_ptr>(m, "
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:98: error: template argument 2 is
> invalid
>  py::class_ std::unique_ptr>(m, "DRAM
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:101: error: 'm' was not declared
> in this scope
>  :class_ std::unique_ptr>(m, "DRAMCtr
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:14: error: 'py' is not a class,
> namespace, or enumeration
>  .def(py::init<>())
>   ^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:23: error: expected
> primary-expression before '>' token
>  .def(py::init<>())
>^
> build/X86/python/_m5/param_DRAMCtrl.cc:60:25: error: expected
> primary-expression before ')' token
>  .def(py::init<>())
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:5: error: 'py' is not a class,
> namespace, or enumeration
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
>  ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:24: error: expected
> primary-expression before ',' token
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:40: error: expected
> primary-expression before ',' token
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:68: error: the value of 'py' is
> not usable in a constant expression
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:59:86: note: 'py' was not declared
> 'constexpr'
>  py::class_ std::unique_ptr>(m, "
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:80: error: type/value mismatch at
> argument 2 in template parameter list for 'template
> class std::unique_ptr'
>  py::class_ py::nodelete>>(m, "DRAMCtrl")
>
> ^
> build/X86/python/_m5/param_DRAMCtrl.cc:132:80: note:   expected a type, got
> 'py'
> build/X86/python/_m5/param_DRAMCtrl.cc: At global scope:
> build/X86/python/_m5/param_DRAMCtrl.cc:135:1: error: expected unqualified-id
> at end of input
>  };
>  ^
> scons: *** [build/X86/python/_m5/param_DRAMCtrl.o] Error 1
> scons: building terminated because of errors.
>
>
> --
> Mao Ye,
>
> ___
> gem5-users mailing list
> gem5-users@gem5.org
> http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users