derek/gem5
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

mem-ruby: Expose MessageBuffer methods

Browse Source 
SLICC interface for checking the capacity of MessageBuffers

Change-Id: I28e2d22a405d33fcbe6a183dffc31bd936fa26c4
Signed-off-by: Tiago Mück <tiago.muck@arm.com>
Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/31271
Reviewed-by: Jason Lowe-Power <power.jg@gmail.com>
Maintainer: Jason Lowe-Power <power.jg@gmail.com>
Tested-by: kokoro <noreply+kokoro@google.com>
This commit is contained in:
Tiago Mück
2020-05-28 12:31:03 -05:00
parent cb48ce2a34
commit 544bf8bde7
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/mem/ruby/protocol/RubySlicc_Types.sm
View File

@@ -48,7 +48,15 @@
// undefined declaration error.
//
external_type(MessageBuffer, buffer="yes", inport="yes", outport="yes");
structure(MessageBuffer, buffer="yes", inport="yes", outport="yes",
external = "yes", primitive="yes") {
// NOTE: it's recommended to use SLICC's built in resource stall management.
// These functions are mostly for including resource utilization info
// in debug traces dumped by the protocol.
bool areNSlotsAvailable(int n, Tick curTime);
int getSize(Tick curTime);
}
external_type(Scalar, primitive="yes");
structure(OutPort, external = "yes", primitive="yes") {