| svt_chi_system_protocol_flow_ctrl_copyback_resp_same_txnid_diff_rn_same_hn_virtual_scenario |
- This scenario requires atleast two HN-F nodes to be present in the Interconnect.
-
This scenario requires atleast two initiating active and participating RN-Fs.
-
Program the any two randomly selected RN-F's to drive a MakeUnique transaction targeted to randomly selected same HN-F.
-
Program the above selected RN-F's to drive a CopyBack transactions simultaneously with same TxnId and address same as of MakeUnique transactions.
-
Check the HN-F responds with same Txnid to respective RN-F's.
-
Program a randomly selected RN-F to drive a ReadShared transaction to verify CopyBack transaction.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN-F node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN-F node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
-
This scenario does not support EVICT and WRITEEVICTFULL transactions.
|
| svt_chi_system_protocol_flow_ctrl_copyback_resp_same_txnid_diff_rn_diff_hn_virtual_scenario |
- This scenario requires atleast two HN-F nodes to be present in the Interconnect.
-
This scenario requires atleast two initiating active and participating RN-Fs.
-
Program the any two randomly selected RN-F's to drive a MakeUnique transaction targeted to randomly selected different HN-F.
-
Program the above selected RN-F's to drive a CopyBack transactions simultaneously with same TxnId and address same as of MakeUnique transactions.
-
Check the HN-F responds with same Txnid to respective RN-F's.
-
Program a randomly selected RN-F to drive a ReadShared transaction to verify CopyBack transaction.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN-F node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
-
This scenario does not support EVICT and WRITEEVICTFULL transactions.
|
| svt_chi_system_protocol_flow_ctrl_write_resp_same_txnid_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
Program two MAKEUNIQUE transaction from one randomly selected RN targeted to same HN.
-
Program two randomly selected different RN VIP to drive a write transaction with same Txnid simultaneously to randomly selected same HN Nodes of MAKEUNIQUE transactions.
-
Check the HN responds with same Txnid to respective RN's.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_write_resp_same_txnid_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two HN nodes to be present in the Interconnect.
|
| svt_chi_system_protocol_flow_ctrl_cmo_resp_same_txnid_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
Program two MakeUnique transactions from one randomly selected RN_F targeted to same HN Node.
-
Program two randomly selected different RN VIP to drive any CMO type transaction with same Txnid simultaneously to above selected same HN Node of MakeUnique transactions.
-
Check the HN responds with same Txnid to respective RN's.
-
For CleanShared, CleanInvalid transactions, Program Read transactions from above first selected RN_F to compare Read data with data of above MakeUnique transactions
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_cmo_resp_same_txnid_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two HN nodes to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
Program two MakeUnique transactions from one randomly selected RN_F targeted to different HN Nodes.
-
Program two randomly selected different RN VIP to drive any CMO type transaction with same Txnid simultaneously to above selected same HN Nodes of MakeUnique transactions.
-
Check the HN's respond with same Txnid to respective RN's.
-
For CleanShared, CleanInvalid transactions, Program Read transactions from above first selected RN_F to compare Read data with data of above MakeUnique transactions
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_read_resp_same_txnid_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's:
-
if select_rn_f_node is progammed through vmm_opts, RN's selected will be of RN-F type
-
if select_rn_i_node is progammed through vmm_opts, RN's selected will be of RN-I type
-
if neither select_rn_f_node or select_rn_i_node is progammed through vmm_opts,then the RN's selected will be of RN-F type
-
Optionally program a randomly selected RN to send two MAKEUNIQUE transaction targeted to randomly selected same target IDs when number of RN_F is 3 or more incase of RN_F test or number of RN_F is atleast 1 incase of RN_I test.
-
Program other two randomly selected RN's to send a read type coherent transaction with same TxnID simultaneously to above selected same target IDs of MAKEUNIQUE transactions if MAKEQNIQUE transaction is sent for initilization.
-
If MAKEQNIQUE transaction is not sent for initilization program two randomly selected different RN's to send a read type coherent transaction with same TxnID simultaneously to randomly selected same target IDs.
-
The scenario also checks that the HN's responds with same TxnId to respective RN's.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_read_resp_same_txnid_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two different HN nodes to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's:
-
if select_rn_f_node is progammed through vmm_opts, RN's selected will be of RN-F type
-
if select_rn_i_node is progammed through vmm_opts, RN's selected will be of RN-I type
-
if neither select_rn_f_node or select_rn_i_node is progammed through vmm_opts,then the RN's selected will be of RN-F type
-
Optionally program a randomly selected RN to send two MAKEUNIQUE transaction targeted to randomly selected different target IDs when number of RN-F is 3 or more incase of RN-F test or number of RN-F is atleast 1 incase of RN-I test.
-
Program other two randomly selected RN's to send a read type coherent transaction with same TxnID simultaneously to above selected different target IDs of MAKEUNIQUE transactions if MAKEQNIQUE transaction is sent for initilization.
-
If MAKEQNIQUE transaction is not sent for initilization program two randomly selected different RN's to send a read type coherent transaction with same TxnID simultaneously to randomly selected different target IDs.
-
The scenario also checks that the HN's responds with same TxnId to respective RN's.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_copyback_outstanding_same_rn_same_hn_virtual_scenario |
- This scenario requires atleast one HN node to be present in the Interconnect.
-
This scenario requires atleast one initiating active and participating RN-F.
-
Inititate maximum(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) number of MAKEUNIQUE transactions from existing active and participating RN-F, to perform cache initialization to a randomly selected HN.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of COPYBACK type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 from the initiating RN-F to the randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at HN.
-
Also, the RN-F will not transmit CopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the scenario.
-
The addresses of these COPYBACK transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
The RN-F of these COPYBACK transactions are such that:
-
Same as RN-F from which cache initialization is performed
-
Once the RN-F receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the CopyBackWrData for these transactions can be resumed from RN-F.
-
The scenario also checks that the HN responds properly for all 256 outstanding COPYBACK type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 is the node index from which the transactions are initiated
-
This RN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
-
This scenario does not support EVICT and WRITEEVICTFULL transactions.
|
| svt_chi_system_protocol_flow_ctrl_copyback_outstanding_diff_rn_same_hn_virtual_scenario |
- This scenario requires atleast one HN-F node to be present in the Interconnect.
-
This scenario requires atleast two initiating active and participating RN-Fs.
-
Inititate 128 (`SVT_CHI_MAX_NUM_OUTSTANDING_XACT/2) number of MAKEUNIQUE transactions from existing active and participating different RN-Fs, to perform cache initialization to a randomly selected HN-F.
-
Initiate 128(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT/2) number of COPYBACK type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 from initiating RN-Fs to randomly selected HN-F in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN-F.
-
Also,the RN-Fs will not transmit CopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the scenario.
-
The addresses of these COPYBACK transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
The RN-Fs of these COPYBACK transactions are such that:
-
Same as RN-Fs from which cache initialization is performed
-
Once the RN-Fs receives the responses for all the outstanding transactions from the HN-F, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the CopyBackWrData for these transactions can be resumed from RN-Fs.
-
The scenario also checks that the HN-F responds properly for all 256 outstanding COPYBACK type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN-F node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN-F node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
-
This scenario does not support EVICT and WRITEEVICTFULL transactions.
|
| svt_chi_system_protocol_flow_ctrl_copyback_outstanding_diff_rn_diff_hn_virtual_scenario |
- This scenario requires atleast two HN-F nodes to be present in the Interconnect.
-
This scenario requires atleast two initiating active and participating RN-Fs.
-
Inititate maximum number of MAKEUNIQUE transactions from existing active and participating different RN-Fs, to perform cache initialization to a randomly selected different HN-F's.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of COPYBACK type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 from initiating RN-Fs to randomly selected HN-F's in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at two different HN-F's.
-
Also, the RN-Fs will not transmit CopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the scenario.
-
The addresses of these COPYBACK transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
The RN-Fs of these COPYBACK transactions are such that:
-
Same as RN-Fs from which cache initialization is performed
-
Once the RN-Fs receives the responses for all the outstanding transactions from HN-F's, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the CopyBackWrData for these transactions can be resumed from RN-Fs.
-
The scenario also checks that the HN-F's responds properly for all 256 outstanding COPYBACK type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN-F node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN-F node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
-
This scenario does not support EVICT and WRITEEVICTFULL transactions.
|
| svt_chi_system_protocol_flow_ctrl_write_outstanding_same_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires one initiating active and participating RN.
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of Write type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 from initiating RN to randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN.
-
Also, the RN will not transmit NonCopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the scenario.
-
The addresses of these write transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the RN receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the NonCopyBackWrData for these transactions can be resumed from RN.
-
The scenario also checks that the HN responds properly for all 256 outstanding write type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 is the node index from which the transactions are initiated
-
This RN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_write_outstanding_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate 128(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT/2) number of Write type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 from each of the two initiating RN's to the randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN.
-
Also, both the RN's will not transmit NonCopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the scenario.
-
The addresses of these write transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the RN's receive the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the NonCopyBackWrData for these transactions can be resumed from both the RN's.
-
The scenario also checks that the HN responds properly for all 256 outstanding write type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_write_outstanding_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two HN nodes to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
If another active and participating RN-F exists, perform cache initialization to two randomly selected HN's.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of Write type transactions with svt_chi_rn_transaction :: suspend_wr_data set to 1 each from both the initiating RN's to randomly selected two HN's from each of the RN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at both the HN's.
-
Also, the RN's will not transmit NonCopyBackWrData corresponding to these transactions until svt_chi_rn_transaction :: suspend_wr_data is set to 0 from the sequence.
-
The addresses of these write transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting both the HN's
-
Once the RN's receive the responses for all the outstanding transactions from both of the HN's, svt_chi_rn_transaction :: suspend_wr_data is set to 0 for all the outstanding transactions. This ensures that the NonCopyBackWrData for these transactions can be resumed from the RN's.
-
Check that both of the HN's respond properly for all 512 outstanding write type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_cmo_outstanding_same_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires one initiating active and participating RN.
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of CMO type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from initiating RN to randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN.
-
Also, the RN will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario.
-
The addresses of these CMO transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the RN receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from RN.
-
The scenario also checks that the HN responds properly for all 256 outstanding CMO type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 is the node index from which the transactions are initiated
-
This RN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_cmo_outstanding_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate 128(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT/2) number of CMO type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from selected initiating RN to randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN.
-
Also, the selected RN's will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario.
-
The addresses of these CMO transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the selected RN's receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from selected RN's.
-
The scenario also checks that the HN responds properly for all 256 outstanding CMO type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_cmo_outstanding_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two HN nodes to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's.
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected two different HN's.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of CMO type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from selected initiating RN to randomly selected different HN's in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the two different selected HN's.
-
Also, the selected RN's will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario.
-
The addresses of these CMO transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the different HN's
-
Once the selected RN's receives the responses for all the outstanding transactions from selected HN's, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from selected RN's.
-
The scenario also checks that the selected HN's responds properly for all 256 outstanding CMO type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_read_outstanding_same_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires one initiating active and participating RN:
-
if select_rn_f_node is progammed through vmm_opts, RN selected will be of RN-F type
-
if select_rn_i_node is progammed through vmm_opts, RN selected will be of RN-I type
-
if neither select_rn_f_node or select_rn_i_node is progammed through vmm_opts,then the RN selected will be of RN-F type
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of Read type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from initiating RN to randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the HN.
-
Also, the RN will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario.
-
The addresses of these Read transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the RN receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from RN.
-
The scenario also checks that the HN responds properly for all 256 outstanding Read type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 is the node index from which the transactions are initiated
-
This RN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_read_outstanding_diff_rn_same_hn_virtual_scenario |
- This scenario requires at least one HN node to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's:
-
if select_rn_f_node is progammed through vmm_opts, RN's selected will be of RN-F type
-
if select_rn_i_node is progammed through vmm_opts, RN's selected will be of RN-I type
-
if neither select_rn_f_node or select_rn_i_node is progammed through vmm_opts,then the RN's selected will be of RN-F type
-
If another active and participating RN-F exists, perform cache initialization to a randomly selected HN.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of Read type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from two initiating RN's to randomly selected HN in non blocking mode.
-
This ensures that the maximum outstanding transaction limit is reached at the same HN.
-
Also, the two different RN's will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario.
-
The addresses of these Read transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the same HN
-
Once the RN receives the responses for all the outstanding transactions from HN, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from different RN's.
-
The scenario also checks that the HN responds properly for all 256 outstanding Read type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 is the node index for which the transactions are targeted
-
This HN node index can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_protocol_flow_ctrl_read_outstanding_diff_rn_diff_hn_virtual_scenario |
- This scenario requires at least two different HN nodes to be present in the Interconnect.
-
This scenario requires two initiating active and participating RN's:
-
if select_rn_f_node is progammed through vmm_opts, RN's selected will be of RN-F type
-
if select_rn_i_node is progammed through vmm_opts, RN's selected will be of RN-I type
-
if neither select_rn_f_node or select_rn_i_node is progammed through vmm_opts,then the RN's selected will be of RN-F type
-
If another active and participating RN-F exists, perform cache initialization to randomly selected two different HN's.
-
Initiate maximum number(`SVT_CHI_MAX_NUM_OUTSTANDING_XACT) of Read type transactions with svt_chi_rn_transaction :: suspend_comp_ack set to 1 from two initiating RN's to randomly selected different HN's in non blocking mode
-
This ensures that the maximum outstanding transaction limit is reached at the two different HN's
-
Also, the two different RN's will not transmit CompAck corresponding to these transactions until svt_chi_rn_transaction :: suspend_comp_ack is set to 0 from the scenario
-
The addresses of these Read transactions are such that:
-
Same as initialized cache line addresses if cache initialization is performed
-
Otherwise, random addresses targeting the different HN's
-
Once the RN receives the responses for all the outstanding transactions from different HN's, svt_chi_rn_transaction :: suspend_comp_ack is set to 0 for all the outstanding transactions. This ensures that the CompAck for these transactions can be resumed from different RN's.
-
The scenario also checks that the different HN's responds properly for all 256 outstanding Read type transactions and these are completed successfully.
-
svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_0 and svt_chi_system_base_virtual_scenario :: initiating_rn_node_index_1 are the node indices from which the transactions are initiated
-
These RN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 3 for initiating_rn_node_idx_0: vmm_opts :: set_int("@%*:initiating_rn_node_idx_0",3)
-
svt_chi_system_base_virtual_scenario :: target_hn_node_index_0 and svt_chi_system_base_virtual_scenario :: target_hn_node_index_1 are the node indices for which the transactions are targeted
-
These HN node indices can be programmed through vmm_opts from the test
-
The programmed value overwrites randomized value
-
Usage to program a value of 4 for target_hn_node_index_0: vmm_opts :: set_int("@%*:target_hn_node_idx_0", 4)
|
| svt_chi_system_single_node_makeinvalid_virtual_scenario |
This sequence/scenario initiates MakeInvalid transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each MakeInvalid transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_cleaninvalid_virtual_scenario |
This sequence/scenario initiates CleanInvalid transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each CleanInvalid transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_cleanshared_virtual_scenario |
This sequence/scenario initiates CleanShared transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each CleanShared transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writeuniqueptl_virtual_scenario |
This sequence/scenario initiates WriteUniquePtl transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. |
| svt_chi_system_single_node_writeuniquefull_virtual_scenario |
This sequence/scenario initiates WriteUniqueFull transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. |
| svt_chi_system_single_node_writenosnpptl_virtual_scenario |
This sequence/scenario initiates WriteNoSnpPtl transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. |
| svt_chi_system_single_node_writenosnpfull_virtual_scenario |
This sequence/scenario initiates WriteNoSnpFull transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. |
| svt_chi_system_single_node_evict_virtual_scenario |
This sequence/scenario initiates Evict transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each Evict transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writecleanptl_virtual_scenario |
This sequence/scenario initiates WriteCleanPtl transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each WriteCleanPtl transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writecleanfull_virtual_scenario |
This sequence/scenario initiates WriteCleanFull transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each WriteCleanFull transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writeevictfull_virtual_scenario |
This sequence/scenario initiates WriteEvictFull transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each WriteEvictFull transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writebackptl_virtual_scenario |
This sequence/scenario initiates WriteBackPlt transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each WriteBackPlt transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_writebackfull_virtual_scenario |
This sequence/scenario initiates WriteBackFull transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each WriteBackFull transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_makeunique_virtual_scenario |
This sequence/scenario initiates MakeUique transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each MakeUnique transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_cleanunique_virtual_scenario |
This sequence/scenario initiates CleanUnique transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each CleanUnique transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_readunique_virtual_scenario |
This sequence/scenario initiates ReadUnique transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each ReadUnique transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_readclean_virtual_scenario |
This sequence/scenario initiates ReadClean transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each ReadClean transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_readnosnp_virtual_scenario |
This sequence/scenario initiates ReadNoSnp transaction from the RN node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each ReadNoSnp transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_readonce_virtual_scenario |
This sequence/scenario initiates ReadOnce transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each ReadOnce transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_readshared_virtual_scenario |
This sequence/scenario initiates ReadShared transaction from the RN-F node specified with node_index, which can be a random node or a specific node configured by the user. Before sending each ReadShard transaction, cachelines of peer node are initialized to random, valid states. |
| svt_chi_system_single_node_rn_coherent_transaction_base_virtual_scenario |
Description-Unavailable |
| svt_chi_system_base_virtual_scenario |
This sequence/scenario creates a reporter reference |
| svt_chi_system_rn_coherent_transaction_base_virtual_scenario |
Description-Unavailable |
| svt_chi_rn_read_type_transaction_directed_scenario |
Abstract: This class defines a sequence that sends Write type transactions. Execution phase: main_phase Sequencer: RN agent sequencer |
| svt_chi_rn_cmo_type_transaction_directed_scenario |
Abstract: This class defines a sequence that sends CMO type transactions. Execution phase: main_phase Sequencer: RN agent sequencer |
| svt_chi_rn_write_type_transaction_directed_scenario |
Abstract: This class defines a sequence that sends Write type transactions. Execution phase: main_phase Sequencer: RN agent sequencer |
| svt_chi_rn_copyback_type_transaction_directed_scenario |
Abstract: This class defines a sequence that sends CopyBack type transactions. Execution phase: main_phase Sequencer: RN agent sequencer |
| svt_chi_rn_makeunique_cache_initialization_directed_scenario |
Abstract: Sends MAKEUNIQUE transactions from an RN Execution phase: main_phase Sequencer: RN agent generator |
| svt_chi_system_base_scenario |
Description-Unavailable |
| svt_chi_rn_f_port_chi_rn_f_port_pair_concurrent_overlapping_non_atomic_xacts_cov_container |
The covergroup container class used to define the covergroups across multiple RN ports when concurrent overlapping transactions are observed across pair of RN_F nodes. class itself contain cover groups. The constructor of this class gets instance name handle , RN-F node indices as arguments which is used to set the instance name of the respective covergroup constructed. |
| svt_chi_rn_f_port_chi_rn_i_port_pair_concurrent_overlapping_xacts_cov_container |
The covergroup container class used to define the covergroups across multiple RN ports when concurrent overlapping transactions are observed across RN_F and RN-I nodes. class itself contain cover groups. The constructor of this class gets instance name handle , RN-F and RN-I node indices as arguments which is used set the instance name of the respective covergroup constructed. |
| vmm_tlm_analysis_export_sn_xact |
Description-Unavailable |
| vmm_tlm_analysis_export_rn_snp_xact |
Description-Unavailable |
| vmm_tlm_analysis_export_rn_coh_xact |
Description-Unavailable |
| svt_chi_sn_scenario_gen_callbacks |
Scenario generator callback class extension to cause the randomization of the scenario to wait for the request |
| svt_chi_sn_transaction_base_scenario |
Scenario generator callback class extension to cause the randomization of the scenario to wait for the request |
| svt_chi_sn_scenario_gen |
This class is an extention of the default generated SN transaction scenario generator. This class adds a blocking transport export class which is connected to the blocking transport port in the SN monitor. The svt_chi_sn_group
class is responsible for connecting these ports if the group is configured as an active component. |
| vmm_tlm_analysis_export_rx_req_flit |
Description-Unavailable |
| svt_chi_ic_rn_link_cb_exec_common |
CHI Protocol Driver callback execution class defines the cb_exec methods supported by the CHI Link component. |
| vmm_tlm_analysis_export_rx_snp_flit |
Description-Unavailable |
| vmm_tlm_analysis_export_rx_rsp_flit |
Description-Unavailable |
| vmm_tlm_analysis_export_rx_dat_flit |
Description-Unavailable |
| vmm_tlm_analysis_export_tx_dat_flit |
Description-Unavailable |
| vmm_tlm_analysis_export_tx_rsp_flit |
Description-Unavailable |
| vmm_tlm_analysis_export_tx_req_flit |
Description-Unavailable |
| svt_chi_coverage_per_src_id_container |
Description-Unavailable |
| svt_chi_node_pmu |
Base class for all common files for the AMBA CHI VIP. |
| svt_chi_link_rxla_deactivate_state |
Class implementing the RXLA state machine RXLA_DEACTIVATE state. |
| svt_chi_link_rxla_run_state |
Class implementing the RXLA state machine RXLA_RUN state. |
| svt_chi_link_rxla_activate_state |
Class implementing the RXLA state machine RXLA_ACTIVATE state. |
| svt_chi_link_rxla_stop_state |
Class implementing the RXLA state machine RXLA_STOP state. |
| svt_chi_link_txla_deactivate_state |
Class implementing the TXLA state machine TXLA_DEACTIVATE state. |
| svt_chi_link_txla_run_state |
Class implementing the TXLA state machine TXLA_RUN state. |
| svt_chi_link_txla_activate_state |
Class implementing the TXLA state machine TXLA_ACTIVATE state. |
| svt_chi_link_txla_stop_state |
Class implementing the TXLA state machine TXLA_STOP state. |
| svt_chi_link_rxla_fsm |
Class implementing the RXLA state machine. |
| svt_chi_link_txla_fsm |
Class implementing the TXLA state machine. |
| svt_chi_scenario_coverage |
Class containing the coverage groups |
| svt_chi_scenario_coverage_database |
Description-Unavailable |
| svt_chi_load_followed_by_store_followed_by_store_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Load followed by Store followed by Store |
| svt_chi_load_followed_by_store_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Load followed by Store |
| svt_chi_dvmop_tlbi_followed_by_cmo_followed_by_dvmop_tlbi_followed_by_dvmop_sync_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI followed by CMO followed by DVMOp TLBI followed by DVMOp SYNC Transaction |
| svt_chi_dvmop_tlbi_followed_by_cmo_followed_by_dvmop_sync_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI followed by CMO followed by DVMOp SYNC Transaction |
| svt_chi_dvmop_tlbi_followed_by_cancel_dvmop_tlbi_followed_by_non_dvmop_of_same_txnid_followed_by_dvmop_sync_followed_by_cancel_dvmop_sync_followed_by_dvmop_sync_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_dvmop_tlbi_followed_by_dvmop_sync_followed_by_dvmop_sync_followed_by_dvmop_tlbi_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI followed by DVMOp SYNC Transaction followed by DVMOp SYNC Transaction followed by DVMOp TLBI Transaction |
| svt_chi_dvmop_tlbi_followed_by_cancel_dvmop_tlbi_followed_by_dvmop_tlbi_of_same_txnid_followed_by_dvmop_sync_followed_by_cancel_dvmop_sync_followed_by_dvmop_sync_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_dvmop_tlbi_transaction_followed_by_retry_dvmop_tlbi_transaction_followed_by_dvmop_sync_transaction_followed_by_retry_dvmop_sync_transaction_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_dvmop_tlbi_followed_by_dvmop_tlbi_followed_by_dvmop_sync_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI followed by DVMOp TLBI followed by DVMOp SYNC Transaction |
| svt_chi_dvmop_tlbi_outstanding_followed_by_dvmop_tlbi_followed_by_retry_dvmop_tlbi_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI outstanding followed by DVMOp TLBI followed by Retry DVMOp SYNC Transaction |
| svt_chi_dvmop_tlbi_outstanding_followed_by_dvmop_sync_followed_by_retry_dvmop_sync_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI outstanding followed by DVMOp Sync followed by Retry DVMOp SYNC Transaction |
| svt_chi_dvmop_tlbi_followed_by_dvmop_sync_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
DVMOp TLBI followed by DVMOp SYNC Transaction |
| svt_chi_cancel_transaction_after_two_normal_transaction_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_retry_transaction_after_two_normal_transaction_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_cancel_transaction_between_two_normal_transaction_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_retry_transaction_between_two_normal_transaction_of_same_txnid_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
|
| svt_chi_three_read_request_ordering_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
CHI-B Spec Figure 2-23::Three Read Request Order Example Ordered READ#1 ---> Ordered READ#2 ---> Retry Ordered READ#2 ---> Ordered READ#3 |
| svt_chi_back2back_transaction_same_src_id_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
'N' times Back2Back CHI Transactions of Same Source-ID |
| svt_chi_no_ordering_rd_after_two_non_no_ordering_transaction_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Non No-Ordering Order Write/Read followed by Non No-Ordering Order Write/Read followed by No-Ordering Read with Same Address/Different-Different Address. |
| svt_chi_back2back_order_type_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
'N' times Back2Back Order Type Transaction |
| svt_chi_read_followed_by_write_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Read followed by Write |
| svt_chi_read_followed_by_read_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Read followed by Read |
| svt_chi_write_followed_by_write_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Write followed by Write |
| svt_chi_write_followed_by_read_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Write followed by Read |
| svt_chi_req_ordered_wr_followed_by_req_ordered_rd_pattern_sequence |
This Class represents the following pattern sequence, which needs to be scanned within the CHI Transactions.
Request Order Write followed by Request Order Read |
| chi_rn_write_read_directed_scenario |
Description-Unavailable |
| svt_chi_memory |
Description-Unavailable |
| svt_chi_system_monitor_chi_coherent_snoop_association_callback_data |
The data object of this class will be used as an argument to 'post_process_associated_snoop_transactions_to_chi_coherent_xact' callback in CHI system monitor to provide the required information to tweak the chi coherent and snoop transaction association performed by the CHI system monitor. All the required arguments are the members of this class. |
| svt_chi_system_monitor_l2_icn_to_l1_icn_snoop_transaction_activity_callback_data |
The data object of this class will be used as argument for callbacks of CHI system monitor related to:
-
L1-ICN downstream Snoop transaction started.
-
L1-ICN downstream Snoop transaction ended.
-
L1-ICN upstream Snoop transaction started.
-
L1-ICN upstream Snoop transaction ended.
All the required arguments are the members of this class. Any additional arguments if required can be added to this class. |
| svt_chi_system_monitor_l1_icn_to_l2_icn_rn_transaction_activity_callback_data |
The data object of this class will be used as argument for callbacks of CHI system monitor related to:
-
L1-ICN downstream RN transaction started.
-
L1-ICN downstream RN transaction ended.
-
L1-ICN upstream RN transaction started.
-
L1-ICN upstream RN transaction ended.
All the required arguments are the members of this class. Any additional arguments if required can be added to this class. |
| svt_chi_system_monitor_end_of_simulation_callback_data |
The data object of this class will be used as argument to end_of_simulation callbacks of CHI system monitor. All the required arguments of end_of_simulation callbacks are the members of this class. The additional arguments, if required to be added to end_of_simulation callback, can be added to this class. |
| svt_chi_system_monitor_callback_data |
Base class for system monitor callback data object. The data object of this class will be used as argument to newly aaded callbacks in CHI system monitor. |
| svt_chi_callback_data |
Base class for callback data object. The data object of this class will be used as argument to newly aaded callbacks in CHI VIP. |
| svt_chi_sn_transaction_ms_scenario |
Description-Unavailable |
| svt_chi_exclusive_monitor |
Description-Unavailable |
| svt_chi_system_monitor_exclusive_sequence_transaction_activity_callback_data |
The data object of this class will be used as argument for callback in CHI system monitor to set the expectation for the excluisve load/store transaction All the required arguments are the members of this class. Any additional arguments if required can be added to this class. |
| svt_chi_rn_transaction_ms_scenario |
Description-Unavailable |
| svt_chi_flit_ms_scenario |
Description-Unavailable |
| svt_chi_transaction_ms_scenario |
Description-Unavailable |
| svt_chi_rn_snoop_transaction_ms_scenario |
Description-Unavailable |
| svt_chi_snoop_transaction_ms_scenario |
Description-Unavailable |
| svt_chi_link_service_ms_scenario |
Description-Unavailable |
| svt_chi_protocol_service_ms_scenario |
Description-Unavailable |
| svt_chi_system_domain_item |
Description-Unavailable |
| svt_chi_hn_addr_range |
Defines a range of address identified by a starting address(start_addr) and end address(end_addr). |
| svt_axi_vmm_pkg |
Description-Unavailable |
| svt_amba_common_vmm_pkg |
Description-Unavailable |
| svt_vmm_pkg |
Description-Unavailable |
| vmm_std_lib |
Description-Unavailable |
| svt_axi_cache |
This class is used to model a single cache. |
| svt_axi_cache_line |
This class is used to represent a single cache line. It is intended to be used to create a sparse array of stored cache line data, with each element of the array representing a full cache line in the cache. The object is initilized with, and stores the information about the index, the address associated with this cache line, the corresponding data and the status of the cache line. |
| svt_amba_addr_mapper |
Description-Unavailable |
| svt_vmm_pkg |
Description-Unavailable |
| vmm_std_lib |
Description-Unavailable |
| vmm_std_lib |
Description-Unavailable |