Skip to content
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

ldata/sdata for atomic and CSR data tracing #166

Open
jaydipdmehta opened this issue Oct 24, 2024 · 0 comments
Open

ldata/sdata for atomic and CSR data tracing #166

jaydipdmehta opened this issue Oct 24, 2024 · 0 comments

Comments

@jaydipdmehta
Copy link

jaydipdmehta commented Oct 24, 2024

Etrace spec has below text:

Atomic and CSR accesses have either both load and store data, or store data and an operand. For CSRs
and unified atomics, both values are reported via data, with the store data in the LSBs and the load
data or operand in the MSBs

Its unclear what is carried on 'ldata' and 'sdata' of data trace interface for split load signalling, as above text mentions about LSBs and MSBs which seems to be valid for unified signalling? Can such information be detailed?

Meanwhile, can you clarify if below sentences are true for split signalling?

  • For CSRs and atomic, 'sdata' carries data thats getting written to address 'daddr' and ldata carries data thats originally read from address 'daddr'?
  • For csrrc and csrrs, data being written to csr is reported or rs1 content are expected to be reported on data trace interface?

Thanks,
Jaydip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant