-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spli load data only packet #175
Comments
Jaydip,
When you say "data only", you mean by setting trTeDataControl.trTeDAtaNoAddr to 1?
This mode is intended to save bandwidth in a small set of use cases where you don't need to include the load/store address in the trace because you already know what it is. For example, if you have set the trace filtering to only trace loads/stores from a particular instruction or set of instructions , which always accesses the same (known) address or sequence or addresses. I don't anticipate this to be widely used.
If the split load data is returned in order then I don't see any that it matters whether you are using unified or split data only - the data can be associated with the addresses by virtue of the order of the trace packets. However, if the order in which split data is returned is not the same as the order in which the addresses were issued then you cannot use data only trace - you will need to the load addresses (and associated lrid) in order to correctly determine which load was responsible for which data.
Iain
From: jaydipdmehta ***@***.***>
Sent: 22 November 2024 08:08
To: riscv-non-isa/riscv-trace-spec ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [riscv-non-isa/riscv-trace-spec] Spli load data only packet (Issue #175)
When encoder is configured to generate data only packets, how would decoder associate this packet with iaddr on intruction trace intf? Split load data may come later, post instruction retirement. If split load address pkt is generated, using lrid/lid corresponding iaddr could be found. With split load data only packets generation, how to find corresponding iaddr?
Thanks,
Jaydip
-
Reply to this email directly, view it on GitHub<#175>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALQOPSVPFNJI2XDWCDAQP5T2B3Q6TAVCNFSM6AAAAABSIY4DOOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGY4DEMRWHEYTEOA>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When encoder is configured to generate data only packets, how would decoder associate this packet with iaddr on intruction trace intf? Split load data may come later, post instruction retirement. If split load address pkt is generated, using lrid/lid corresponding iaddr could be found. With split load data only packets generation, how to find corresponding iaddr?
Thanks,
Jaydip
The text was updated successfully, but these errors were encountered: