mem-ruby: Add descriptions to the CHI DVM symbols.
This commit adds `desc` descriptions to the new symbols introduced with CHI DVM support. The generation of the SLICC HTML documentation requires each symbol to have a description, so a build with `SLICC_HTML=True` will fail without this change. Change-Id: I06f3bdd33edd1ff6e4bec35b01a460b9359ed9f6 Reviewed-on: https://gem5-review.googlesource.com/c/public/gem5/+/60869 Maintainer: Bobby Bruce <bbruce@ucdavis.edu> Reviewed-by: Jason Lowe-Power <power.jg@gmail.com> Tested-by: kokoro <noreply+kokoro@google.com>
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
/*
|
||||
* Copyright (c) 2021 ARM Limited
|
||||
* Copyright (c) 2021-2022 ARM Limited
|
||||
* All rights reserved
|
||||
*
|
||||
* The license below extends only to copyright in the software and shall
|
||||
@@ -344,10 +344,10 @@ machine(MachineType:Cache, "Cache coherency protocol") :
|
||||
PCrdGrant_PoC_Hazard, desc="";
|
||||
|
||||
// Events triggered by incoming DVM messages
|
||||
SnpDvmOpSync_P1;
|
||||
SnpDvmOpSync_P2;
|
||||
SnpDvmOpNonSync_P1;
|
||||
SnpDvmOpNonSync_P2;
|
||||
SnpDvmOpSync_P1, desc="";
|
||||
SnpDvmOpSync_P2, desc="";
|
||||
SnpDvmOpNonSync_P1, desc="";
|
||||
SnpDvmOpNonSync_P2, desc="";
|
||||
|
||||
// Events triggered by incoming data response messages
|
||||
// See CHIDataType in CHi-msg.sm for descriptions
|
||||
|
||||
@@ -162,8 +162,8 @@ machine(MachineType:MiscNode, "CHI Misc Node for handling and distrbuting DVM op
|
||||
AllocRequest, desc="Allocates a TBE for a request. Triggers a retry if table is full";
|
||||
AllocRequestWithCredit, desc="Allocates a TBE for a request. Always succeeds. Used when a client is retrying after being denied.";
|
||||
|
||||
SnpResp_I;
|
||||
NCBWrData;
|
||||
SnpResp_I, desc="";
|
||||
NCBWrData, desc="";
|
||||
|
||||
// Retry handling
|
||||
SendRetryAck, desc="Send RetryAck";
|
||||
@@ -182,9 +182,9 @@ machine(MachineType:MiscNode, "CHI Misc Node for handling and distrbuting DVM op
|
||||
// any queued action and is not expecting responses/data. The transaction
|
||||
// is finalized and the next stable state is stored in the cache/directory
|
||||
// See the processNextState and makeFinalState functions
|
||||
Final;
|
||||
Final, desc="";
|
||||
|
||||
null;
|
||||
null, desc="";
|
||||
}
|
||||
|
||||
////////////////////////////////////////////////////////////////////////////
|
||||
|
||||
Reference in New Issue
Block a user