Searched hist:6899 (Results 1 - 14 of 14) sorted by relevance

/gem5/src/mem/ruby/common/
H A DSubBlock.hh6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
/gem5/src/mem/ruby/system/
H A DSequencer.py6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
H A DSequencer.hh6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
H A DRubyPort.hh6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
H A DRubyPort.cc6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
H A DSequencer.cc6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
/gem5/src/arch/mips/linux/
H A Dprocess.cc8697:6899ea99a5cb Thu Jan 12 09:59:00 EST 2012 Deyuan Guo <guodeyuan@tsinghua.org.cn> mips: compatibility between MIPS_SE and cross compiler from CodeSorcery
/gem5/src/mem/
H A Drequest.hh6899:f8057af86bf7 Fri Jan 29 23:29:00 EST 2010 Brad Beckmann <Brad.Beckmann@amd.com> ruby: added the GEMS ruby tester
/gem5/src/cpu/simple/
H A Dtiming.hh5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.
H A Datomic.hh5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.
H A Dbase.hh5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.
H A Dbase.cc5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.
H A Dtiming.cc5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.
H A Datomic.cc5496:6899b894166f Tue Jul 01 10:24:00 EDT 2008 Ali Saidi <saidi@eecs.umich.edu> After a checkpoint (and thus a stats reset), the not_idle_fraction/notIdleFraction statistic is really wrong.
The notIdleFraction statistic isn't updated when the statistics reset, probably because the cpu Status information
was pulled into the atomic and timing cpus. This changeset pulls Status back into the BaseSimpleCPU object. Anyone
care to comment on the odd naming of the Status instance? It shouldn't just be status because that is confusing
with Port::Status, but _status seems a bit strage too.

Completed in 314 milliseconds