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
|
|
|
# Copyright (c) 2010-2013 ARM Limited
|
2010-08-23 18:18:40 +02:00
|
|
|
# All rights reserved.
|
|
|
|
#
|
|
|
|
# The license below extends only to copyright in the software and shall
|
|
|
|
# not be construed as granting a license to any other intellectual
|
|
|
|
# property including but not limited to intellectual property relating
|
|
|
|
# to a hardware implementation of the functionality of the software
|
|
|
|
# licensed hereunder. You may use the software subject to the license
|
|
|
|
# terms below provided that you ensure that this notice is replicated
|
|
|
|
# unmodified and in its entirety in all distributions of the software,
|
|
|
|
# modified or unmodified, in source code or in binary form.
|
|
|
|
#
|
2007-01-03 06:52:30 +01:00
|
|
|
# Copyright (c) 2006-2007 The Regents of The University of Michigan
|
2006-08-16 20:42:44 +02:00
|
|
|
# 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: Ali Saidi
|
|
|
|
|
2009-09-23 00:24:16 +02:00
|
|
|
import optparse
|
|
|
|
import sys
|
2006-08-16 20:42:44 +02:00
|
|
|
|
|
|
|
import m5
|
2009-09-23 00:24:16 +02:00
|
|
|
from m5.defines import buildEnv
|
|
|
|
from m5.objects import *
|
|
|
|
from m5.util import addToPath, fatal
|
2008-06-13 07:09:06 +02:00
|
|
|
|
2009-09-23 00:24:16 +02:00
|
|
|
addToPath('../common')
|
2008-06-13 07:09:06 +02:00
|
|
|
|
2006-08-16 20:42:44 +02:00
|
|
|
from FSConfig import *
|
|
|
|
from SysPaths import *
|
|
|
|
from Benchmarks import *
|
2006-10-27 22:32:26 +02:00
|
|
|
import Simulation
|
2010-02-25 19:13:40 +01:00
|
|
|
import CacheConfig
|
2013-08-19 09:52:34 +02:00
|
|
|
import MemConfig
|
2006-10-30 22:51:46 +01:00
|
|
|
from Caches import *
|
2012-03-28 18:01:53 +02:00
|
|
|
import Options
|
2006-10-30 20:01:34 +01:00
|
|
|
|
2006-08-16 20:42:44 +02:00
|
|
|
parser = optparse.OptionParser()
|
2012-03-28 18:01:53 +02:00
|
|
|
Options.addCommonOptions(parser)
|
|
|
|
Options.addFSOptions(parser)
|
2006-10-24 00:07:51 +02:00
|
|
|
|
2006-08-16 20:42:44 +02:00
|
|
|
(options, args) = parser.parse_args()
|
|
|
|
|
|
|
|
if args:
|
|
|
|
print "Error: script doesn't take any positional arguments"
|
|
|
|
sys.exit(1)
|
|
|
|
|
2006-10-24 00:07:51 +02:00
|
|
|
# driver system CPU is always simple... note this is an assignment of
|
2006-10-17 20:08:49 +02:00
|
|
|
# a class, not an instance.
|
2006-10-24 00:07:51 +02:00
|
|
|
DriveCPUClass = AtomicSimpleCPU
|
|
|
|
drive_mem_mode = 'atomic'
|
2006-10-17 20:08:49 +02:00
|
|
|
|
2013-04-22 19:20:32 +02:00
|
|
|
# Check if KVM support has been enabled, we might need to do VM
|
|
|
|
# configuration if that's the case.
|
|
|
|
have_kvm_support = 'BaseKvmCPU' in globals()
|
|
|
|
def is_kvm_cpu(cpu_class):
|
|
|
|
return have_kvm_support and cpu_class != None and \
|
|
|
|
issubclass(cpu_class, BaseKvmCPU)
|
|
|
|
|
2006-11-02 01:25:09 +01:00
|
|
|
# system under test can be any CPU
|
|
|
|
(TestCPUClass, test_mem_mode, FutureClass) = Simulation.setCPUClass(options)
|
2006-08-16 20:42:44 +02:00
|
|
|
|
2013-04-22 19:20:33 +02:00
|
|
|
# Match the memories with the CPUs, the driver system always simple,
|
|
|
|
# and based on the options for the test system
|
|
|
|
DriveMemClass = SimpleMemory
|
|
|
|
TestMemClass = Simulation.setMemClass(options)
|
|
|
|
|
2006-08-16 20:42:44 +02:00
|
|
|
if options.benchmark:
|
2006-10-17 20:08:49 +02:00
|
|
|
try:
|
|
|
|
bm = Benchmarks[options.benchmark]
|
|
|
|
except KeyError:
|
2006-08-16 20:42:44 +02:00
|
|
|
print "Error benchmark %s has not been defined." % options.benchmark
|
|
|
|
print "Valid benchmarks are: %s" % DefinedBenchmarks
|
|
|
|
sys.exit(1)
|
|
|
|
else:
|
|
|
|
if options.dual:
|
2012-04-17 00:51:26 +02:00
|
|
|
bm = [SysConfig(disk=options.disk_image, mem=options.mem_size), SysConfig(disk=options.disk_image, mem=options.mem_size)]
|
2006-08-16 20:42:44 +02:00
|
|
|
else:
|
2012-04-17 00:51:26 +02:00
|
|
|
bm = [SysConfig(disk=options.disk_image, mem=options.mem_size)]
|
2006-10-17 20:08:49 +02:00
|
|
|
|
2009-04-26 11:04:32 +02:00
|
|
|
np = options.num_cpus
|
|
|
|
|
2009-09-23 00:24:16 +02:00
|
|
|
if buildEnv['TARGET_ISA'] == "alpha":
|
2013-08-19 09:52:27 +02:00
|
|
|
test_sys = makeLinuxAlphaSystem(test_mem_mode, bm[0])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == "mips":
|
2013-08-19 09:52:27 +02:00
|
|
|
test_sys = makeLinuxMipsSystem(test_mem_mode, bm[0])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == "sparc":
|
2013-08-19 09:52:27 +02:00
|
|
|
test_sys = makeSparcSystem(test_mem_mode, bm[0])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == "x86":
|
2013-08-19 09:52:27 +02:00
|
|
|
test_sys = makeLinuxX86System(test_mem_mode, options.num_cpus, bm[0])
|
2010-08-23 18:18:40 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == "arm":
|
2013-08-19 09:52:27 +02:00
|
|
|
test_sys = makeArmSystem(test_mem_mode, options.machine_type, bm[0],
|
|
|
|
options.dtb_filename,
|
2013-04-22 19:20:33 +02:00
|
|
|
bare_metal=options.bare_metal)
|
2013-10-17 17:20:45 +02:00
|
|
|
if options.enable_context_switch_stats_dump:
|
|
|
|
test_sys.enable_context_switch_stats_dump = True
|
2006-12-05 01:37:50 +01:00
|
|
|
else:
|
2012-06-07 15:05:30 +02:00
|
|
|
fatal("Incapable of building %s full system!", buildEnv['TARGET_ISA'])
|
2006-12-05 01:37:50 +01:00
|
|
|
|
2013-08-19 09:52:28 +02:00
|
|
|
# Create a top-level voltage domain
|
|
|
|
test_sys.voltage_domain = VoltageDomain(voltage = options.sys_voltage)
|
|
|
|
|
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
|
|
|
# Create a source clock for the system and set the clock period
|
2013-08-19 09:52:28 +02:00
|
|
|
test_sys.clk_domain = SrcClockDomain(clock = options.sys_clock,
|
|
|
|
voltage_domain = test_sys.voltage_domain)
|
|
|
|
|
|
|
|
# Create a CPU voltage domain
|
|
|
|
test_sys.cpu_voltage_domain = VoltageDomain()
|
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
|
|
|
|
|
|
|
# Create a source clock for the CPUs and set the clock period
|
2013-08-19 09:52:28 +02:00
|
|
|
test_sys.cpu_clk_domain = SrcClockDomain(clock = options.cpu_clock,
|
|
|
|
voltage_domain =
|
|
|
|
test_sys.cpu_voltage_domain)
|
2013-06-27 11:49:49 +02:00
|
|
|
|
2006-12-23 06:51:19 +01:00
|
|
|
if options.kernel is not None:
|
|
|
|
test_sys.kernel = binary(options.kernel)
|
|
|
|
|
|
|
|
if options.script is not None:
|
|
|
|
test_sys.readfile = options.script
|
|
|
|
|
2012-01-10 01:08:20 +01:00
|
|
|
test_sys.init_param = options.init_param
|
|
|
|
|
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
|
|
|
# For now, assign all the CPUs to the same clock domain
|
|
|
|
test_sys.cpu = [TestCPUClass(clk_domain=test_sys.cpu_clk_domain, cpu_id=i)
|
|
|
|
for i in xrange(np)]
|
2007-10-08 21:19:58 +02:00
|
|
|
|
2013-04-22 19:20:32 +02:00
|
|
|
if is_kvm_cpu(TestCPUClass) or is_kvm_cpu(FutureClass):
|
|
|
|
test_sys.vm = KvmVM()
|
|
|
|
|
2009-09-15 06:19:40 +02:00
|
|
|
if options.caches or options.l2cache:
|
2013-06-27 11:49:49 +02:00
|
|
|
# By default the IOCache runs at the system clock
|
|
|
|
test_sys.iocache = IOCache(addr_ranges = test_sys.mem_ranges)
|
2012-02-13 12:43:09 +01:00
|
|
|
test_sys.iocache.cpu_side = test_sys.iobus.master
|
|
|
|
test_sys.iocache.mem_side = test_sys.membus.slave
|
2012-01-17 19:55:09 +01:00
|
|
|
else:
|
2013-01-07 19:05:38 +01:00
|
|
|
test_sys.iobridge = Bridge(delay='50ns', ranges = test_sys.mem_ranges)
|
2012-02-13 12:43:09 +01:00
|
|
|
test_sys.iobridge.slave = test_sys.iobus.master
|
|
|
|
test_sys.iobridge.master = test_sys.membus.slave
|
2007-10-08 21:19:58 +02:00
|
|
|
|
2012-04-03 09:50:14 +02:00
|
|
|
# Sanity check
|
2012-10-26 12:42:45 +02:00
|
|
|
if options.fastmem:
|
|
|
|
if TestCPUClass != AtomicSimpleCPU:
|
|
|
|
fatal("Fastmem can only be used with atomic CPU!")
|
|
|
|
if (options.caches or options.l2cache):
|
|
|
|
fatal("You cannot use fastmem in combination with caches!")
|
2012-04-03 09:50:14 +02:00
|
|
|
|
2006-10-18 06:15:11 +02:00
|
|
|
for i in xrange(np):
|
2007-08-09 00:43:12 +02:00
|
|
|
if options.fastmem:
|
2012-04-03 09:50:14 +02:00
|
|
|
test_sys.cpu[i].fastmem = True
|
2012-03-09 15:59:27 +01:00
|
|
|
if options.checker:
|
|
|
|
test_sys.cpu[i].addCheckerCpu()
|
2013-01-07 19:05:35 +01:00
|
|
|
test_sys.cpu[i].createThreads()
|
2012-03-09 15:59:27 +01:00
|
|
|
|
|
|
|
CacheConfig.config_cache(options, test_sys)
|
2013-08-19 09:52:34 +02:00
|
|
|
MemConfig.config_mem(options, test_sys)
|
2013-08-19 09:52:27 +02:00
|
|
|
|
2006-08-16 20:42:44 +02:00
|
|
|
if len(bm) == 2:
|
2009-09-23 00:24:16 +02:00
|
|
|
if buildEnv['TARGET_ISA'] == 'alpha':
|
2013-08-19 09:52:27 +02:00
|
|
|
drive_sys = makeLinuxAlphaSystem(drive_mem_mode, bm[1])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == 'mips':
|
2013-08-19 09:52:27 +02:00
|
|
|
drive_sys = makeLinuxMipsSystem(drive_mem_mode, bm[1])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == 'sparc':
|
2013-08-19 09:52:27 +02:00
|
|
|
drive_sys = makeSparcSystem(drive_mem_mode, bm[1])
|
2009-09-23 00:24:16 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == 'x86':
|
2013-08-19 09:52:27 +02:00
|
|
|
drive_sys = makeX86System(drive_mem_mode, np, bm[1])
|
2010-08-23 18:18:40 +02:00
|
|
|
elif buildEnv['TARGET_ISA'] == 'arm':
|
2013-08-19 09:52:27 +02:00
|
|
|
drive_sys = makeArmSystem(drive_mem_mode, options.machine_type, bm[1])
|
2012-01-10 01:08:20 +01:00
|
|
|
|
2013-08-19 09:52:28 +02:00
|
|
|
# Create a top-level voltage domain
|
|
|
|
drive_sys.voltage_domain = VoltageDomain(voltage = options.sys_voltage)
|
|
|
|
|
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
|
|
|
# Create a source clock for the system and set the clock period
|
|
|
|
drive_sys.clk_domain = SrcClockDomain(clock = options.sys_clock)
|
|
|
|
|
2013-08-19 09:52:28 +02:00
|
|
|
# Create a CPU voltage domain
|
|
|
|
drive_sys.cpu_voltage_domain = VoltageDomain()
|
|
|
|
|
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
|
|
|
# Create a source clock for the CPUs and set the clock period
|
2013-08-19 09:52:28 +02:00
|
|
|
drive_sys.cpu_clk_domain = SrcClockDomain(clock = options.cpu_clock,
|
|
|
|
voltage_domain =
|
|
|
|
drive_sys.cpu_voltage_domain)
|
2013-06-27 11:49:49 +02:00
|
|
|
|
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
|
|
|
drive_sys.cpu = DriveCPUClass(clk_domain=drive_sys.cpu_clk_domain,
|
|
|
|
cpu_id=0)
|
2013-01-07 19:05:35 +01:00
|
|
|
drive_sys.cpu.createThreads()
|
2012-03-01 18:37:02 +01:00
|
|
|
drive_sys.cpu.createInterruptController()
|
2011-02-04 05:23:00 +01:00
|
|
|
drive_sys.cpu.connectAllPorts(drive_sys.membus)
|
2007-08-09 00:43:12 +02:00
|
|
|
if options.fastmem:
|
2012-04-03 09:50:14 +02:00
|
|
|
drive_sys.cpu.fastmem = True
|
2007-08-01 23:39:16 +02:00
|
|
|
if options.kernel is not None:
|
|
|
|
drive_sys.kernel = binary(options.kernel)
|
2013-01-07 19:05:38 +01:00
|
|
|
|
2013-04-22 19:20:32 +02:00
|
|
|
if is_kvm_cpu(DriveCPUClass):
|
|
|
|
drive_sys.vm = KvmVM()
|
|
|
|
|
Bridge: Remove NACKs in the bridge and unify with packet queue
This patch removes the NACKing in the bridge, as the split
request/response busses now ensure that protocol deadlocks do not
occur, i.e. the message-dependency chain is broken by always allowing
responses to make progress without being stalled by requests. The
NACKs had limited support in the system with most components ignoring
their use (with a suitable call to panic), and as the NACKs are no
longer needed to avoid protocol deadlocks, the cleanest way is to
simply remove them.
The bridge is the starting point as this is the only place where the
NACKs are created. A follow-up patch will remove the code that deals
with NACKs in the endpoints, e.g. the X86 table walker and DMA
port. Ultimately the type of packet can be complete removed (until
someone sees a need for modelling more complex protocols, which can
now be done in parts of the system since the port and interface is
split).
As a consequence of the NACK removal, the bridge now has to send a
retry to a master if the request or response queue was full on the
first attempt. This change also makes the bridge ports very similar to
QueuedPorts, and a later patch will change the bridge to use these. A
first step in this direction is taken by aligning the name of the
member functions, as done by this patch.
A bit of tidying up has also been done as part of the simplifications.
Surprisingly, this patch has no impact on any of the
regressions. Hence, there was never any NACKs issued. In a follow-up
patch I would suggest changing the size of the bridge buffers set in
FSConfig.py to also test the situation where the bridge fills up.
2012-08-22 17:39:58 +02:00
|
|
|
drive_sys.iobridge = Bridge(delay='50ns',
|
2013-01-07 19:05:38 +01:00
|
|
|
ranges = drive_sys.mem_ranges)
|
2012-02-14 09:41:53 +01:00
|
|
|
drive_sys.iobridge.slave = drive_sys.iobus.master
|
|
|
|
drive_sys.iobridge.master = drive_sys.membus.slave
|
2007-08-01 23:39:16 +02:00
|
|
|
|
2013-08-19 09:52:27 +02:00
|
|
|
# Create the appropriate memory controllers and connect them to the
|
|
|
|
# memory bus
|
2013-08-19 09:52:33 +02:00
|
|
|
drive_sys.mem_ctrls = [DriveMemClass(range = r)
|
2013-08-19 09:52:27 +02:00
|
|
|
for r in drive_sys.mem_ranges]
|
|
|
|
for i in xrange(len(drive_sys.mem_ctrls)):
|
|
|
|
drive_sys.mem_ctrls[i].port = drive_sys.membus.master
|
|
|
|
|
2012-01-10 01:08:20 +01:00
|
|
|
drive_sys.init_param = options.init_param
|
2012-01-28 16:24:34 +01:00
|
|
|
root = makeDualRoot(True, test_sys, drive_sys, options.etherdump)
|
2006-08-16 20:42:44 +02:00
|
|
|
elif len(bm) == 1:
|
2012-01-28 16:24:34 +01:00
|
|
|
root = Root(full_system=True, system=test_sys)
|
2006-08-16 20:42:44 +02:00
|
|
|
else:
|
|
|
|
print "Error I don't know how to create more than 2 systems."
|
|
|
|
sys.exit(1)
|
|
|
|
|
2011-01-19 20:48:00 +01:00
|
|
|
if options.timesync:
|
|
|
|
root.time_sync_enable = True
|
|
|
|
|
2011-12-01 09:15:26 +01:00
|
|
|
if options.frame_capture:
|
|
|
|
VncServer.frame_capture = True
|
|
|
|
|
2012-06-07 15:05:31 +02:00
|
|
|
Simulation.setWorkCountOptions(test_sys, options)
|
2006-11-02 01:25:09 +01:00
|
|
|
Simulation.run(options, root, test_sys, FutureClass)
|