Figure out how to best test periherals, CSR and interrupts

[jdupak]

No description provided.

[KotorinMinami]

I am not entirely sure about the specific aspects of testing peripherals, CSRs, and interrupts that you are referring to. If you are talking about testing the behavior of the emulator in these areas, from my perspective, here are some thoughts:

• From the CSR perspective, we know that CSR read/write behaviors are defined in the RISC-V spec, including WLRL, WARL, and other behaviors. The emulator should ensure these behaviors operate correctly.

  • WLRL behavior can be tested like a black box, where we create test cases based on the spec for reading and writing various CSRs, including equivalence class and boundary condition testing. This would involve testing the relationship between the CSR values and their corresponding behaviors.

  • For WARL behavior, testing depends more on the specific implementation of the emulator. The constraints defined in the spec are quite loose, allowing for significant discussion space.

• As for interrupt testing, we could construct corresponding interrupt triggers to test if their behaviors are normal. Additionally, we should test priority and nesting issues related to interrupts. We could base these tests on the spec and then adapt them according to our specific implementation.

I hope my thoughts are helpful to you. If so, perhaps we can discuss these topics in more detail. If I have misunderstood your requirements, I apologize sincerely.