2007-03-11 08:00:54 +01:00
|
|
|
# -*- mode:python -*-
|
|
|
|
|
|
|
|
|
|
# Copyright (c) 2006 The Regents of The University of Michigan
|
|
|
|
|
# All rights reserved.
|
|
|
|
|
#
|
|
|
|
|
# Redistribution and use in source and binary forms, with or without
|
|
|
|
|
# modification, are permitted provided that the following conditions are
|
|
|
|
|
# met: redistributions of source code must retain the above copyright
|
|
|
|
|
# notice, this list of conditions and the following disclaimer;
|
|
|
|
|
# redistributions in binary form must reproduce the above copyright
|
|
|
|
|
# notice, this list of conditions and the following disclaimer in the
|
|
|
|
|
# documentation and/or other materials provided with the distribution;
|
|
|
|
|
# neither the name of the copyright holders nor the names of its
|
|
|
|
|
# contributors may be used to endorse or promote products derived from
|
|
|
|
|
# this software without specific prior written permission.
|
|
|
|
|
#
|
|
|
|
|
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
|
|
|
# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
|
|
|
# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
|
|
|
# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
|
|
|
# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
|
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
|
|
|
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
|
|
|
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
|
|
|
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
|
|
|
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
|
|
|
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
|
#
|
|
|
|
|
# Authors: Nathan Binkert
|
|
|
|
|
|
|
|
|
|
Import('*')
|
|
|
|
|
|
2008-10-11 08:47:42 +02:00
|
|
|
SimObject('BaseTLB.py')
|
2012-08-21 11:49:01 +02:00
|
|
|
SimObject('ClockedObject.py')
|
2007-05-28 04:21:17 +02:00
|
|
|
SimObject('Root.py')
|
sim: Add the notion of clock domains to all ClockedObjects
This patch adds the notion of source- and derived-clock domains to the
ClockedObjects. As such, all clock information is moved to the clock
domain, and the ClockedObjects are grouped into domains.
The clock domains are either source domains, with a specific clock
period, or derived domains that have a parent domain and a divider
(potentially chained). For piece of logic that runs at a derived clock
(a ratio of the clock its parent is running at) the necessary derived
clock domain is created from its corresponding parent clock
domain. For now, the derived clock domain only supports a divider,
thus ensuring a lower speed compared to its parent. Multiplier
functionality implies a PLL logic that has not been modelled yet
(create a separate clock instead).
The clock domains should be used as a mechanism to provide a
controllable clock source that affects clock for every clocked object
lying beneath it. The clock of the domain can (in a future patch) be
controlled by a handler responsible for dynamic frequency scaling of
the respective clock domains.
All the config scripts have been retro-fitted with clock domains. For
the System a default SrcClockDomain is created. For CPUs that run at a
different speed than the system, there is a seperate clock domain
created. This domain incorporates the CPU and the associated
caches. As before, Ruby runs under its own clock domain.
The clock period of all domains are pre-computed, such that no virtual
functions or multiplications are needed when calling
clockPeriod. Instead, the clock period is pre-computed when any
changes occur. For this to be possible, each clock domain tracks its
children.
2013-06-27 11:49:49 +02:00
|
|
|
SimObject('ClockDomain.py')
|
2013-08-19 09:52:28 +02:00
|
|
|
SimObject('VoltageDomain.py')
|
2013-09-04 19:22:57 +02:00
|
|
|
SimObject('System.py')
|
2007-05-28 04:21:17 +02:00
|
|
|
|
2011-10-31 01:38:11 +01:00
|
|
|
Source('arguments.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('async.cc')
|
|
|
|
|
Source('core.cc')
|
|
|
|
|
Source('debug.cc')
|
|
|
|
|
Source('eventq.cc')
|
2013-11-25 18:21:00 +01:00
|
|
|
Source('global_event.cc')
|
libm5: Create a libm5 static library for embedding m5.
This should allow m5 to be more easily embedded into other simulators.
The m5 binary adds a simple main function which then calls into the m5
libarary to start the simulation. In order to make this work
correctly, it was necessary embed python code directly into the
library instead of the zipfile hack. This is because you can't just
append the zipfile to the end of a library the way you can a binary.
As a result, Python files that are part of the m5 simulator are now
compile, marshalled, compressed, and then inserted into the library's
data section with a certain symbol name. Additionally, a new Importer
was needed to allow python to get at the embedded python code.
Small additional changes include:
- Get rid of the PYTHONHOME stuff since I don't think anyone ever used
it, and it just confuses things. Easy enough to add back if I'm wrong.
- Create a few new functions that are key to initializing and running
the simulator: initSignals, initM5Python, m5Main.
The original code for creating libm5 was inspired by a patch Michael
Adler, though the code here was done by me.
2008-08-04 03:19:54 +02:00
|
|
|
Source('init.cc')
|
2011-04-15 19:44:44 +02:00
|
|
|
Source('main.cc', main=True, skip_lib=True)
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('root.cc')
|
|
|
|
|
Source('serialize.cc')
|
2012-11-02 17:32:01 +01:00
|
|
|
Source('drain.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('sim_events.cc')
|
|
|
|
|
Source('sim_object.cc')
|
|
|
|
|
Source('simulate.cc')
|
|
|
|
|
Source('stat_control.cc')
|
sim: Add the notion of clock domains to all ClockedObjects
This patch adds the notion of source- and derived-clock domains to the
ClockedObjects. As such, all clock information is moved to the clock
domain, and the ClockedObjects are grouped into domains.
The clock domains are either source domains, with a specific clock
period, or derived domains that have a parent domain and a divider
(potentially chained). For piece of logic that runs at a derived clock
(a ratio of the clock its parent is running at) the necessary derived
clock domain is created from its corresponding parent clock
domain. For now, the derived clock domain only supports a divider,
thus ensuring a lower speed compared to its parent. Multiplier
functionality implies a PLL logic that has not been modelled yet
(create a separate clock instead).
The clock domains should be used as a mechanism to provide a
controllable clock source that affects clock for every clocked object
lying beneath it. The clock of the domain can (in a future patch) be
controlled by a handler responsible for dynamic frequency scaling of
the respective clock domains.
All the config scripts have been retro-fitted with clock domains. For
the System a default SrcClockDomain is created. For CPUs that run at a
different speed than the system, there is a seperate clock domain
created. This domain incorporates the CPU and the associated
caches. As before, Ruby runs under its own clock domain.
The clock period of all domains are pre-computed, such that no virtual
functions or multiplications are needed when calling
clockPeriod. Instead, the clock period is pre-computed when any
changes occur. For this to be possible, each clock domain tracks its
children.
2013-06-27 11:49:49 +02:00
|
|
|
Source('clock_domain.cc')
|
2013-08-19 09:52:28 +02:00
|
|
|
Source('voltage_domain.cc')
|
2013-09-04 19:22:57 +02:00
|
|
|
Source('system.cc')
|
2010-11-20 01:00:39 +01:00
|
|
|
|
2013-09-04 19:22:57 +02:00
|
|
|
if env['TARGET_ISA'] != 'null':
|
|
|
|
|
SimObject('InstTracer.py')
|
2011-10-30 08:32:54 +01:00
|
|
|
SimObject('Process.py')
|
2010-11-20 01:00:39 +01:00
|
|
|
Source('faults.cc')
|
2011-10-30 08:32:54 +01:00
|
|
|
Source('process.cc')
|
2010-11-20 01:00:39 +01:00
|
|
|
Source('pseudo_inst.cc')
|
2013-09-04 19:22:57 +02:00
|
|
|
Source('syscall_emul.cc')
|
2007-08-28 03:30:58 +02:00
|
|
|
Source('tlb.cc')
|
2007-05-28 04:21:17 +02:00
|
|
|
|
2011-06-03 02:36:21 +02:00
|
|
|
DebugFlag('Checkpoint')
|
|
|
|
|
DebugFlag('Config')
|
2012-08-15 16:38:08 +02:00
|
|
|
DebugFlag('Drain')
|
2011-06-03 02:36:21 +02:00
|
|
|
DebugFlag('Event')
|
|
|
|
|
DebugFlag('Fault')
|
|
|
|
|
DebugFlag('Flow')
|
|
|
|
|
DebugFlag('IPI')
|
|
|
|
|
DebugFlag('IPR')
|
|
|
|
|
DebugFlag('Interrupt')
|
|
|
|
|
DebugFlag('Loader')
|
2013-06-03 13:21:21 +02:00
|
|
|
DebugFlag('PseudoInst')
|
2011-06-03 02:36:21 +02:00
|
|
|
DebugFlag('Stack')
|
|
|
|
|
DebugFlag('SyscallVerbose')
|
|
|
|
|
DebugFlag('TimeSync')
|
|
|
|
|
DebugFlag('TLB')
|
|
|
|
|
DebugFlag('Thread')
|
|
|
|
|
DebugFlag('Timer')
|
|
|
|
|
DebugFlag('VtoPhys')
|
|
|
|
|
DebugFlag('WorkItems')
|
sim: Add the notion of clock domains to all ClockedObjects
This patch adds the notion of source- and derived-clock domains to the
ClockedObjects. As such, all clock information is moved to the clock
domain, and the ClockedObjects are grouped into domains.
The clock domains are either source domains, with a specific clock
period, or derived domains that have a parent domain and a divider
(potentially chained). For piece of logic that runs at a derived clock
(a ratio of the clock its parent is running at) the necessary derived
clock domain is created from its corresponding parent clock
domain. For now, the derived clock domain only supports a divider,
thus ensuring a lower speed compared to its parent. Multiplier
functionality implies a PLL logic that has not been modelled yet
(create a separate clock instead).
The clock domains should be used as a mechanism to provide a
controllable clock source that affects clock for every clocked object
lying beneath it. The clock of the domain can (in a future patch) be
controlled by a handler responsible for dynamic frequency scaling of
the respective clock domains.
All the config scripts have been retro-fitted with clock domains. For
the System a default SrcClockDomain is created. For CPUs that run at a
different speed than the system, there is a seperate clock domain
created. This domain incorporates the CPU and the associated
caches. As before, Ruby runs under its own clock domain.
The clock period of all domains are pre-computed, such that no virtual
functions or multiplications are needed when calling
clockPeriod. Instead, the clock period is pre-computed when any
changes occur. For this to be possible, each clock domain tracks its
children.
2013-06-27 11:49:49 +02:00
|
|
|
DebugFlag('ClockDomain')
|
2013-08-19 09:52:28 +02:00
|
|
|
DebugFlag('VoltageDomain')
|
