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

Multiple Clients Writing to Key Vault #674

Open
nodix95 opened this issue Dec 20, 2024 · 0 comments
Open

Multiple Clients Writing to Key Vault #674

nodix95 opened this issue Dec 20, 2024 · 0 comments

Comments

@nodix95
Copy link

nodix95 commented Dec 20, 2024

I have a question about how HW writes to the key vault. It seems to me from the code snippet below, that an input to one key vault register (key_entry_next[entry][dword]) might be an OR-ed result from writes of two different HW clients, if they decide to write to the same place at the same time. Is this intentional, because the SW is not expected to ever do such a thing, or is there a realistic scenario where this could be problematic? It also seems to be a generic code structure used elsewhere, too.

for (int client = 0; client < KV_NUM_WRITE; client++) begin
key_entry_we[entry][dword] |= ((((kv_write[client].write_entry == entry) & (kv_write[client].write_offset
== dword) & kv_write[client].write_en) | flush_keyvault) &
((~lock_wr_q[entry] & ~lock_use_q[entry]) | debugUnlock_or_scan_mode_switch));
key_entry_next[entry][dword] |= flush_keyvault ? debug_value :
kv_write[client].write_en & (kv_write[client].write_entry == entry) ? kv_write[client].write_data : '0;
end

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