Closed sdexter-numa closed 4 years ago
Not currently. You’ll need to hack the code to accomplish this.
On Thu, Sep 26, 2019 at 4:11 PM sdexter-numa notifications@github.com wrote:
Is it possible in Spike to expect User and Supervisor modes to be disabled? This is an issue in my use case, because the Spike logger always expects certain bits of the mstatus CSR to be set, but they will never be set if the riscv processor dut is only in Machine Mode.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/riscv/riscv-isa-sim/issues/336?email_source=notifications&email_token=AAH3XQRXWJ2J5LHTH52IZV3QLS7HRA5CNFSM4I22SBBKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HN4ZBWA, or mute the thread https://github.com/notifications/unsubscribe-auth/AAH3XQSJWEITTIUOJOYHNTDQLS7HRANCNFSM4I22SBBA .
I was able to find a workaround. I'm using google's riscv-dv instruction generator, and it's possible within that to disable some bits in mstatus from ever being set, which means Spike won't take any issue with it.
Is it possible in Spike to expect User and Supervisor modes to be disabled? This is an issue in my use case, because the Spike logger always expects certain bits of the mstatus CSR to be set, but they will never be set if the riscv processor dut is only in Machine Mode.