The best place to see what parameters and ports are on SimObjects is to
look in the src directory for .py files. That's where the SimObjects are
defined. The values in those files are defaults, and not meant for
actually configuring things.
The scripts that are normally used to set up a
hello，Gabe ，Thank you very much ，you are so kind ！
But now I have another questions ，The following code is sequencer.py：
class RubyPort(MemObject):
type = 'RubyPort'
abstract = True
port = VectorPort(M5 port) . 1
version = Param.Int(0, )
I'm not sure what the answer is to many of your questions, but it seems that
a good solution to figuring them out would be to just run some simple
workloads and then look at the config.ini file (default outputted to the
m5out directory) to verify your configuration is what you think it is. At
Thanks very much for the pointers, Steve.
I'm feeling very foolish now. I've worked out the problem and it was my
mistake. I was using a different kernel to the standard one and I'd
updated the relevant line in FSConfig.py in makeLinuxAlphaSystem() but
not in makeLinuxAlphaRubySystem().
I use the command build/ARM_SE/m5.opt --debug-flags=Ruby
configs/example/ruby_se.py，but there is an error ： m5.opt ：error ：no such
option ： --debug-flags
在 2011年5月17日 下午7:47，Korey Sewell ksew...@umich.edu写道：
I'm not sure what the answer is to many of your questions, but it seems
that a good
Thanks. The problem was that writing to the parameter was optimized
out. I have corrected it locally by adding volatile to the parameter
name in m5op.h.
-Gedare
On Tue, May 17, 2011 at 12:36 AM, Ali Saidi sa...@umich.edu wrote:
You'll have to play a compiler trick to make sure it doesn't
Correction: it was sufficient for me to include m5op.h properly.
Before, the compiler was only finding the function (m5_exit) at
link-time, so I suppose that was causing some problem.
On Tue, May 17, 2011 at 1:33 PM, Gedare Bloom ged...@gwmail.gwu.edu wrote:
Thanks. The problem was that writing
You might not be using the latest source. You can either update it, or
try --trace-flags instead of --debug-flags.
Gabe
On 05/17/11 05:22, xuewen zhou wrote:
I use the command build/ARM_SE/m5.opt --debug-flags=Ruby
configs/example/ruby_se.py，but there is an error ： m5.opt ：error
：no such
hello,Korey Sewell
Thank you very much for answering me so kind ! But now I have the same
questions just I ask last time : how could I get the new simObjet's ports
,and how could I
connect the with Ruby system ? and another question is that what is in Ruby
system ? Is it containing network
gem5 has two different memory systems right now, the classic M5 system
and the new Ruby system. I'm not an expert in this area, but I'm
pretty sure you have to use one or the other, not both. I know a
little bit about the classic system and very little about Ruby.
Gabe
Quoting xuewen zhou
Hi
I intend to obtain list of all threads in ruby. Is there this facility in
Gems/Ruby? (For example if there are 5 threads in Ruby, I want to obtain their
threadID and current processor that running this thread).
Thanks.
___
gem5-users mailing list
Hello,
All of the postings on the home page mentioned using GE/M5 with GCC,
as in compiling the simulator, as well as cross compiling programs for
target architectures to run on the simulator. Though no mention is
made of LLVM in this context.
Is is not preferred to use LLVM or has it never
I believe people have use llvm and arm and it has worked. But it doesnt hurt
to try it out right? Makes sure you compile your binary statically and give
it a go. If it doesnt work, I'm sure that others would want llvm support in
gem5 so you can post your problem to the mailing list and see what
13 matches
Mail list logo
