|
|
Post by ptgzxk on Mar 19, 2024 1:41:00 GMT
Assume that an MCTP Endpoint has completed the MCTP over PCIe endpoint discovery (that is, MCTP over PCIe endpoint discovery has been performed). At this time, the host sends a Prepare for Endpoint Discovery request again. In this case, should the Route Type field in the MCTP response message be set to Route to Root Complex, and the Source Endpoint ID field be Assigned Endpoint ID value?
|
|
|
|
Post by pmschoeller on Mar 19, 2024 13:23:06 GMT
Thank you for your feedback and will reply shortly.
|
|
|
|
Post by ptgzxk on Mar 20, 2024 1:44:41 GMT
1.In the MCTP over PCIe VDM Binding specification has the following description: The Source Endpoint ID field Shall be set to the Null Souce EID if the device has not been assigned an EID; otherwise, it shall contain the assigned EID value. Does the Source Endpoint ID field in the MCTP response messages follow this rule (all MCTP control message/NVMe-MI Command)? Does this rule also apply to MCTP over Smbus binding specification?
2.For MCTP over PCIe endpoint discovery, when the MCTP Endpoint receives the Set Endpoint ID command, even if the command operation is not Set Discovered Flag, should the MCTP Endpoint set the discovered flag to 1?
3.Assume that an MCTP Endpoint has completed the MCTP over PCIe endpoint discovery (that is, MCTP over PCIe endpoint discovery has been performed). At this time, the host sends a Prepare for Endpoint Discovery request again. In this case, should the Route Type field in the MCTP response message be set to Route to Root Complex, and the Source Endpoint ID field be Assigned Endpoint ID value?
Please help me clarify these questions.
|
|
|
|
Post by pmschoeller on Apr 2, 2024 13:12:49 GMT
This issue is being tracked by the PMCI WG and will be addressed as part of specification update. Thank you for your submission.
|
|
