IainCRobertson
commented
3 months ago You should really be working from the E-Trace Encapsulation spec, rather than Chapter 7 of the E-Trace spec. The latter is only illustrative, and not part of the standard. The E-Trace Encapsulation TG was set up specifically to produce a formalized standard for the encapsulation.
As noted previously, the length of the timestamp can be any number of bytes and is not limited to 16-bits.
In terms of ATID being only 7 bits, I think the way that is usually handled (in Arm-based systems) is to dynamically allocate the SrcID/ATID at run-time.
Iain
From: zhangdujiao @.> Sent: 31 May 2024 04:39 To: riscv-non-isa/riscv-trace-spec @.> Cc: Subscribed @.***> Subject: [riscv-non-isa/riscv-trace-spec] There is no SRCID filed in ATB Encapsulation (Issue #112)
From the description from Chapter 7, ATB Encapsulation contains:
- A 5-bit field specifying the payload length in bytes
- A bit to indicate whether an optional 16-bit timestamp is present;
- An optional 2-byte timestamp;
- The packet payload. The encapsulation has no SRCID filed. While the ATID is only 7bit width, witch may not be enough, How to solve this problem?
thanks!
- Reply to this email directly, view it on GitHubhttps://github.com/riscv-non-isa/riscv-trace-spec/issues/112, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALQOPSTWSNGQAAN7S26RYDDZE7WFRAVCNFSM6AAAAABISBIK7WVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMZDMOBZHA4DSNQ. You are receiving this because you are subscribed to this thread.Message ID: @.**@.>>
zhangdujiao
From the description from Chapter 7, ATB Encapsulation contains: • A 5-bit field specifying the payload length in bytes • A bit to indicate whether an optional 16-bit timestamp is present; • An optional 2-byte timestamp; • The packet payload. The encapsulation has no SRCID filed. While the ATID is only 7bit width, witch may not be enough, How to solve this problem?
thanks!