From 68ddfab8a4fa6f56c5f8bff6d91facd39abe353b Mon Sep 17 00:00:00 2001 From: Nilay Vaish Date: Thu, 6 Nov 2014 05:42:20 -0600 Subject: ruby: remove the function functionalReadBuffers() This function was added when I had incorrectly arrived at the conclusion that such a function can improve the chances of a functional read succeeding. As was later realized, this is not possible in the current setup. While the code using this function was dropped long back, this function was not. Hence the patch. --- src/mem/ruby/slicc_interface/AbstractController.hh | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) (limited to 'src/mem/ruby/slicc_interface') diff --git a/src/mem/ruby/slicc_interface/AbstractController.hh b/src/mem/ruby/slicc_interface/AbstractController.hh index f30967e48..98fce574f 100644 --- a/src/mem/ruby/slicc_interface/AbstractController.hh +++ b/src/mem/ruby/slicc_interface/AbstractController.hh @@ -76,11 +76,8 @@ class AbstractController : public ClockedObject, public Consumer virtual void recordCacheTrace(int cntrl, CacheRecorder* tr) = 0; virtual Sequencer* getSequencer() const = 0; - //! These functions are used by ruby system to read/write the message - //! queues that exist with in the controller. - //! The boolean return value indicates if the read was performed - //! successfully. - virtual bool functionalReadBuffers(PacketPtr&) = 0; + //! These functions are used by ruby system to read/write the data blocks + //! that exist with in the controller. virtual void functionalRead(const Address &addr, PacketPtr) = 0; //! The return value indicates the number of messages written with the //! data from the packet. -- cgit v1.2.3