DT Based Implementation of GetPerformanceCounterProperties () #2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Dhaval Sharma <[email protected]>
Going forward we would like to make use of DT as much as possible. Going forward this Lib function will be used to retrieve Timer freq instead of PCD. Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Dhaval Sharma <[email protected]>
Signed-off-by: Akshay behl <[email protected]>
cap2k4-rivos
force-pushed
the
dev/dhaval/upstream-dt-hob
branch
2 times, most recently
from
a377032 to
d34942a
Compare
cap2k4-rivos
force-pushed
the
dev/dhaval/upstream-dt-hob
branch
4 times, most recently
from
4bcef7a to
998eef0
Compare
cap2k4-rivos
force-pushed
the
dev/dhaval/upstream-dt-hob
branch
from
998eef0 to
eb5f7cb
Compare
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 11, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 14, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 21, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 29, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 30, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Jul 30, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 4, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 5, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 5, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 6, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 28, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Aug 29, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Sep 2, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Sep 3, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Sep 3, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
cap2k4-rivos
referenced
this pull request
in cap2k4-rivos/edk2
Sep 3, 2025
Implementation is based on https://github.com/riscv-non-isa/riscv-rpmi/tree/main and works in the following way: 1. MM initialization is successful -> call REQFWD_COMPLETE_CURRENT_MESSAGE to yield. (this API will change once we have properly defined the init API for MM) 2. NS domain calls MM_COMMUNICATE, OpenSBI performs context switch (if channel is not capable of SSE) -> MM resumes loop from REQFWD_COMPLETE_CURRENT_MESSAGE. 3. Calls REQFWD_RETRIEVE_CURRENT_MESSAGE. 4. MM handles the request contained in the message. 5. MM calls REQFWD_COMPLETE_CURRENT_MESSAGE. 6. OpenSBI switches to the non-secure domain (as there are no more messages in the queue && SSE is not supported) 7. Go to #2 Signed-off-by: Dhaval Sharma <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.