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

Maximum standard message size vs. NTRACE_MAX_ICNT #71

Open
Graf-Zahl opened this issue Oct 11, 2024 · 1 comment
Open

Maximum standard message size vs. NTRACE_MAX_ICNT #71

Graf-Zahl opened this issue Oct 11, 2024 · 1 comment

Comments

@Graf-Zahl
Copy link

Hi!

NTRACE_MAX_ICNT is 22 but in calculation of maximum message size its maximum is given by 30.
Do I misunderstand something?

Thanks

|I-CNT|NTRACE_MAX_ICNT|22|Usually a smaller value will be sufficient. An overflow bit may be used for efficient I-CNT full detection.

to transmit <<msg_IndirectBranchHistSync,IndirectBranchHistSync>> message which includes TCODE/ SRC/ SYNC/ B-TYPE(5 bytes total), I-CNT(30 bits, 5 bytes), F-ADDR(63 bits, 11 bytes), HIST(32 bits, 6 bytes) TSTAMP(64 bits, 11 bytes).

@mipsrobert
Copy link
Collaborator

Thanks. I am glad someone is reading spec carefully :-). I will refrain form making any changes and wait for formal ratification before doing any changes. I will keep this ticked open until addresses.

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

2 participants