- 05 3月, 2020 1 次提交
-
-
由 Zihao Yu 提交于
* calling setjmp() at the beginning of exec() will reduce performance
-
- 04 3月, 2020 3 次提交
- 03 3月, 2020 3 次提交
- 02 3月, 2020 6 次提交
- 01 3月, 2020 3 次提交
- 29 2月, 2020 2 次提交
- 11 12月, 2019 1 次提交
-
-
由 Zihao Yu 提交于
-
- 10 12月, 2019 3 次提交
-
-
由 Zihao Yu 提交于
* If an RVC instruction is at the end of page boundary, we should not fetch 4 bytes. Otherwise, we may trigger an IPF when fetching the remaining 2 bytes at the beginning of the next page, which is inconsistent with the behavior of the RISC-V priviledged manual. * In such a case, we should first fetch 2 byte. If it is an RVC instruction, then execute it without fetching the remaining 2 bytes. If it is not an RVC instruciton, then fetching the remaining 2 bytes to obtain a 4-byte instruction.
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
* this can help to reduce idle time in Linux
-
- 07 12月, 2019 5 次提交
- 13 11月, 2019 5 次提交
-
-
由 Zihao Yu 提交于
* An illegal instruction will be emulated in M-mode. It may trigger page fault during the emulation. In such a situation, we should record the bad address in mtval instead of stval, and trap into M-mode again. The M-mode handler will distribute this page fault exception to S-mode by software code. * If we do not set mtval in such case, the software handler will distribute the page fault exception with a garbage mtval set to stval, causing kernel panic by a real page fault.
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
* QEMU does not use an LR bit. Is it safe enough?
-
- 11 11月, 2019 8 次提交
-
-
由 William Wang 提交于
-
由 Zihao Yu 提交于
* An AMO instruction may trigger page fault when storing the result back to memory. In such a case, we should not update the dest register. To fix this issue, we delay the register writeback after the store operation.
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-
由 Zihao Yu 提交于
-