You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on expanding the functionality of the RISC-V HPM and during my testing I stumbled upon a "bug" where the value of CSR_MHPMCOUNTER3 as all it's bits set to 1 during the openSBI initialization process. Should it not respect the value defined by the architecture during an HW reset? Or is there any reason why leaving the value as is advantageous?
The text was updated successfully, but these errors were encountered:
Tiago-R
changed the title
CSR_MHPMCOUNTER3 counters initialization on hart_pmu_get_allowed_bits()
CSR_MHPMCOUNTER3 counter initialization on hart_pmu_get_allowed_bits()
Nov 27, 2024
I'm working on expanding the functionality of the RISC-V HPM and during my testing I stumbled upon a "bug" where the value of CSR_MHPMCOUNTER3 as all it's bits set to 1 during the openSBI initialization process. Should it not respect the value defined by the architecture during an HW reset? Or is there any reason why leaving the value as is advantageous?
The text was updated successfully, but these errors were encountered: