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('*')
|
|
|
|
|
|
2013-01-07 19:05:37 +01:00
|
|
|
# Only build the communication if we have support for protobuf as the
|
|
|
|
|
# tracing relies on it
|
|
|
|
|
if env['HAVE_PROTOBUF']:
|
|
|
|
|
SimObject('CommMonitor.py')
|
|
|
|
|
Source('comm_monitor.cc')
|
|
|
|
|
|
2013-09-04 19:22:57 +02:00
|
|
|
SimObject('AbstractMemory.py')
|
2012-09-25 18:49:40 +02:00
|
|
|
SimObject('AddrMapper.py')
|
2007-05-28 04:21:17 +02:00
|
|
|
SimObject('Bridge.py')
|
|
|
|
|
SimObject('Bus.py')
|
2014-03-23 16:12:12 +01:00
|
|
|
SimObject('DRAMCtrl.py')
|
2007-05-28 04:21:17 +02:00
|
|
|
SimObject('MemObject.py')
|
2013-09-04 19:22:57 +02:00
|
|
|
SimObject('SimpleMemory.py')
|
2009-05-11 19:38:46 +02:00
|
|
|
|
2013-09-04 19:22:57 +02:00
|
|
|
Source('abstract_mem.cc')
|
2012-09-25 18:49:40 +02:00
|
|
|
Source('addr_mapper.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('bridge.cc')
|
|
|
|
|
Source('bus.cc')
|
Bus: Split the bus into a non-coherent and coherent bus
This patch introduces a class hierarchy of buses, a non-coherent one,
and a coherent one, splitting the existing bus functionality. By doing
so it also enables further specialisation of the two types of buses.
A non-coherent bus connects a number of non-snooping masters and
slaves, and routes the request and response packets based on the
address. The request packets issued by the master connected to a
non-coherent bus could still snoop in caches attached to a coherent
bus, as is the case with the I/O bus and memory bus in most system
configurations. No snoops will, however, reach any master on the
non-coherent bus itself. The non-coherent bus can be used as a
template for modelling PCI, PCIe, and non-coherent AMBA and OCP buses,
and is typically used for the I/O buses.
A coherent bus connects a number of (potentially) snooping masters and
slaves, and routes the request and response packets based on the
address, and also forwards all requests to the snoopers and deals with
the snoop responses. The coherent bus can be used as a template for
modelling QPI, HyperTransport, ACE and coherent OCP buses, and is
typically used for the L1-to-L2 buses and as the main system
interconnect.
The configuration scripts are updated to use a NoncoherentBus for all
peripheral and I/O buses.
A bit of minor tidying up has also been done.
--HG--
rename : src/mem/bus.cc => src/mem/coherent_bus.cc
rename : src/mem/bus.hh => src/mem/coherent_bus.hh
rename : src/mem/bus.cc => src/mem/noncoherent_bus.cc
rename : src/mem/bus.hh => src/mem/noncoherent_bus.hh
2012-05-31 19:30:04 +02:00
|
|
|
Source('coherent_bus.cc')
|
2014-03-23 16:12:12 +01:00
|
|
|
Source('dram_ctrl.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('mem_object.cc')
|
2011-10-16 14:06:39 +02:00
|
|
|
Source('mport.cc')
|
Bus: Split the bus into a non-coherent and coherent bus
This patch introduces a class hierarchy of buses, a non-coherent one,
and a coherent one, splitting the existing bus functionality. By doing
so it also enables further specialisation of the two types of buses.
A non-coherent bus connects a number of non-snooping masters and
slaves, and routes the request and response packets based on the
address. The request packets issued by the master connected to a
non-coherent bus could still snoop in caches attached to a coherent
bus, as is the case with the I/O bus and memory bus in most system
configurations. No snoops will, however, reach any master on the
non-coherent bus itself. The non-coherent bus can be used as a
template for modelling PCI, PCIe, and non-coherent AMBA and OCP buses,
and is typically used for the I/O buses.
A coherent bus connects a number of (potentially) snooping masters and
slaves, and routes the request and response packets based on the
address, and also forwards all requests to the snoopers and deals with
the snoop responses. The coherent bus can be used as a template for
modelling QPI, HyperTransport, ACE and coherent OCP buses, and is
typically used for the L1-to-L2 buses and as the main system
interconnect.
The configuration scripts are updated to use a NoncoherentBus for all
peripheral and I/O buses.
A bit of minor tidying up has also been done.
--HG--
rename : src/mem/bus.cc => src/mem/coherent_bus.cc
rename : src/mem/bus.hh => src/mem/coherent_bus.hh
rename : src/mem/bus.cc => src/mem/noncoherent_bus.cc
rename : src/mem/bus.hh => src/mem/noncoherent_bus.hh
2012-05-31 19:30:04 +02:00
|
|
|
Source('noncoherent_bus.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('packet.cc')
|
|
|
|
|
Source('port.cc')
|
2012-03-22 11:36:27 +01:00
|
|
|
Source('packet_queue.cc')
|
2007-03-11 08:00:54 +01:00
|
|
|
Source('tport.cc')
|
2012-02-24 17:46:39 +01:00
|
|
|
Source('port_proxy.cc')
|
2013-09-04 19:22:57 +02:00
|
|
|
Source('simple_mem.cc')
|
|
|
|
|
Source('physical.cc')
|
2009-05-11 19:38:46 +02:00
|
|
|
|
2013-09-04 19:22:57 +02:00
|
|
|
if env['TARGET_ISA'] != 'null':
|
|
|
|
|
Source('fs_translating_port_proxy.cc')
|
|
|
|
|
Source('se_translating_port_proxy.cc')
|
2011-10-16 14:06:40 +02:00
|
|
|
Source('page_table.cc')
|
2010-11-20 01:00:39 +01:00
|
|
|
|
2014-03-23 16:11:44 +01:00
|
|
|
if env['HAVE_DRAMSIM']:
|
|
|
|
|
SimObject('DRAMSim2.py')
|
|
|
|
|
Source('dramsim2_wrapper.cc')
|
|
|
|
|
Source('dramsim2.cc')
|
2014-02-18 11:50:53 +01:00
|
|
|
|
Bus: Split the bus into a non-coherent and coherent bus
This patch introduces a class hierarchy of buses, a non-coherent one,
and a coherent one, splitting the existing bus functionality. By doing
so it also enables further specialisation of the two types of buses.
A non-coherent bus connects a number of non-snooping masters and
slaves, and routes the request and response packets based on the
address. The request packets issued by the master connected to a
non-coherent bus could still snoop in caches attached to a coherent
bus, as is the case with the I/O bus and memory bus in most system
configurations. No snoops will, however, reach any master on the
non-coherent bus itself. The non-coherent bus can be used as a
template for modelling PCI, PCIe, and non-coherent AMBA and OCP buses,
and is typically used for the I/O buses.
A coherent bus connects a number of (potentially) snooping masters and
slaves, and routes the request and response packets based on the
address, and also forwards all requests to the snoopers and deals with
the snoop responses. The coherent bus can be used as a template for
modelling QPI, HyperTransport, ACE and coherent OCP buses, and is
typically used for the L1-to-L2 buses and as the main system
interconnect.
The configuration scripts are updated to use a NoncoherentBus for all
peripheral and I/O buses.
A bit of minor tidying up has also been done.
--HG--
rename : src/mem/bus.cc => src/mem/coherent_bus.cc
rename : src/mem/bus.hh => src/mem/coherent_bus.hh
rename : src/mem/bus.cc => src/mem/noncoherent_bus.cc
rename : src/mem/bus.hh => src/mem/noncoherent_bus.hh
2012-05-31 19:30:04 +02:00
|
|
|
DebugFlag('BaseBus')
|
2011-06-03 02:36:21 +02:00
|
|
|
DebugFlag('BusAddrRanges')
|
Bus: Split the bus into a non-coherent and coherent bus
This patch introduces a class hierarchy of buses, a non-coherent one,
and a coherent one, splitting the existing bus functionality. By doing
so it also enables further specialisation of the two types of buses.
A non-coherent bus connects a number of non-snooping masters and
slaves, and routes the request and response packets based on the
address. The request packets issued by the master connected to a
non-coherent bus could still snoop in caches attached to a coherent
bus, as is the case with the I/O bus and memory bus in most system
configurations. No snoops will, however, reach any master on the
non-coherent bus itself. The non-coherent bus can be used as a
template for modelling PCI, PCIe, and non-coherent AMBA and OCP buses,
and is typically used for the I/O buses.
A coherent bus connects a number of (potentially) snooping masters and
slaves, and routes the request and response packets based on the
address, and also forwards all requests to the snoopers and deals with
the snoop responses. The coherent bus can be used as a template for
modelling QPI, HyperTransport, ACE and coherent OCP buses, and is
typically used for the L1-to-L2 buses and as the main system
interconnect.
The configuration scripts are updated to use a NoncoherentBus for all
peripheral and I/O buses.
A bit of minor tidying up has also been done.
--HG--
rename : src/mem/bus.cc => src/mem/coherent_bus.cc
rename : src/mem/bus.hh => src/mem/coherent_bus.hh
rename : src/mem/bus.cc => src/mem/noncoherent_bus.cc
rename : src/mem/bus.hh => src/mem/noncoherent_bus.hh
2012-05-31 19:30:04 +02:00
|
|
|
DebugFlag('CoherentBus')
|
|
|
|
|
DebugFlag('NoncoherentBus')
|
|
|
|
|
CompoundFlag('Bus', ['BaseBus', 'BusAddrRanges', 'CoherentBus',
|
|
|
|
|
'NoncoherentBus'])
|
|
|
|
|
|
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
|
|
|
DebugFlag('Bridge')
|
2012-05-09 10:37:45 +02:00
|
|
|
DebugFlag('CommMonitor')
|
2012-09-21 17:48:13 +02:00
|
|
|
DebugFlag('DRAM')
|
2014-05-10 00:58:48 +02:00
|
|
|
DebugFlag('DRAMState')
|
2011-06-03 02:36:21 +02:00
|
|
|
DebugFlag('LLSC')
|
|
|
|
|
DebugFlag('MMU')
|
|
|
|
|
DebugFlag('MemoryAccess')
|
2012-03-22 11:36:27 +01:00
|
|
|
DebugFlag('PacketQueue')
|
2010-12-01 20:30:04 +01:00
|
|
|
|
2014-02-18 11:50:53 +01:00
|
|
|
DebugFlag("DRAMSim2")
|
