2013-06-27 11:49:49 +02:00
|
|
|
# Copyright (c) 2012-2013 ARM Limited
|
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
|
|
|
# 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-05-28 04:21:17 +02:00
|
|
|
# Copyright (c) 2006-2007 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: Ali Saidi
|
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
|
|
|
# Andreas Hansson
|
2007-05-28 04:21:17 +02:00
|
|
|
|
|
|
|
|
from m5.params import *
|
|
|
|
|
from MemObject import MemObject
|
|
|
|
|
|
|
|
|
|
class Bridge(MemObject):
|
|
|
|
|
type = 'Bridge'
|
2012-11-02 17:32:01 +01:00
|
|
|
cxx_header = "mem/bridge.hh"
|
2012-02-13 12:43:09 +01:00
|
|
|
slave = SlavePort('Slave port')
|
|
|
|
|
master = MasterPort('Master port')
|
2013-06-27 11:49:49 +02:00
|
|
|
req_size = Param.Unsigned(16, "The number of requests to buffer")
|
|
|
|
|
resp_size = Param.Unsigned(16, "The number of responses to buffer")
|
2007-05-28 04:21:17 +02:00
|
|
|
delay = Param.Latency('0ns', "The latency of this bridge")
|
2012-01-17 19:55:09 +01:00
|
|
|
ranges = VectorParam.AddrRange([AllMemory],
|
|
|
|
|
"Address ranges to pass through the bridge")
|
