Port: Add isSnooping to slave port (asking master port)

This patch adds isSnooping to the slave port, and thus avoids going
through getMasterPort to be able to ask the master. Over the course of
the next few patches, all getMasterPort/getSlavePort in Port and
MemObject are to be protocol agnostic, and the snooping is part of the
protocol layer.

The function is already present on the master port, where it is
implemented by the module itself, e.g. a cache. On the slave side, it
is merely asking the connected master port. The same name is used by
both functions despite their difference in behaviour. The initial
design used isMasterSnooping on the slave port side, but the more
verbose function name was later changed.

1 files changed, 7 insertions, 0 deletions

diff --git a/src/mem/port.hh b/src/mem/port.hh
index b93d5d444..49b0e1846 100644
--- a/src/mem/port.hh
+++ b/src/mem/port.hh
@@ -356,6 +356,13 @@ class SlavePort : public Port
     unsigned peerBlockSize() const;
 
     /**
+     * Find out if the peer master port is snooping or not.
+     *
+     * @return true if the peer master port is snooping
+     */
+    bool isSnooping() const { return _masterPort->isSnooping(); }
+
+    /**
      * Called by the owner to send a range change
      */
     void sendRangeChange() const { _masterPort->recvRangeChange(); }