about cfg file

[jerry yin]

Hi,

I'm trying to understand the configure folder. From group mail I found you previously said "A default Sniper run will include base.cfg, nehalem.cfg, gainestown.cfg (in that order)". However, I only find #include instruction from gainestown. Does that implies that all configuration files implicitly override base.cfg, so that you don't have to specify the #include when you want to use base.cfg?

Also, among the config files in the folder, most files seems to be incomplete in terms of a whole system.  For example, nuca-cache.cfg noc.cfg... First, I'm curious what these files are used for. Second, I don't understand why I still could be able to run the simulation with these incomplete configurations like ./run-sniper --benchmarks=splash2-fft-test-4 - c noc?

Thanks,

jer

[Wim Heirman]

Jer,

That's right, base.cfg is added implicitly as the initial configuration file, and provides default values for everything not configured explicitly.

The incomplete files are meant as modifiers for complete files. For instance, -c gainestown -c nuca-cache allows you to model a Gainestown-like configuration that in addition has a NUCA cache. If some of them do work in isolation, that means the combination of it and base.cfg happens to define everything that is needed, but just don't count on this representing any sensible existing hardware architecture.

Regards,

Wim

--
--
--
You received this message because you are subscribed to the Google
Groups "Sniper simulator" group.
To post to this group, send email to snip...@googlegroups.com
To unsubscribe from this group, send email to
snipersim+...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/snipersim?hl=en

---
You received this message because you are subscribed to the Google Groups "Sniper simulator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to snipersim+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jerry yin]

Hi,

One more problem when I do my self configurations. My configuration file (one simple line) is as follows:

#include gainestown

[perf_model/cache]

levels=0

And when I run this configuration with benchmark, I get the fault:

[SNIPER] Start

[SNIPER] Internal exception: Segmentation fault. Access Address = 0x20

[SNIPER] End

[SNIPER] Elapsed time: 0.20 seconds

------------------------------------------------------------

Segmentation fault. Access Address = 0x20

Backtrace:

    cache_cntlr.h:ParametricDramDirectoryMSI::CacheCntlr::setNextCacheCntlr:368

    memory_manager_base.cc:MemoryManagerBase::createMMU:23

    core.cc:__gnu_cxx::__sso_string_base<char, std::char_traits<char>, std::allocator<char> >::_M_is_local:571

    vector.tcc:emplace_back<Core*>:95

    simulator.cc:Simulator::start:96

    simulator.h:Simulator::hideCfg:61

    ??:??:0

    ??:_start:0

------------------------------------------------------------

So I'm just wondering the problem is due to you don't allow the "no cache" mode, or because of the wrong configuration. I'm trying to see what if the configuration file have a conflict. Like on one hand, I set no cache, on the other hand, there is configurations set the cache parameters. Would this be a problem?

Best Wishes

[Wim Heirman]

You need at least two cache levels. It's OK to have configuration settings that are not used or are not even valid, they will just be ignored.

Regards,

Wim

--