[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PATCH v4 24/33] target/nios2: Introduce shadow register sets
From: |
Amir Gonnen |
Subject: |
RE: [PATCH v4 24/33] target/nios2: Introduce shadow register sets |
Date: |
Wed, 9 Mar 2022 14:02:14 +0000 |
Hi Richard,
How does "cpu_crs_R" work?
In your version you hold a pointer to the current register set instead of
copying registers back and forth like I did, which makes sense.
But how does TCG know which set to refer to when it generates code?
It looks like it's always accessing the same cpu_crs_R, so how does it relate
to the correct register set on "shadow_regs"?
In fact, I imagined it would be necessary to change "cpu_get_tb_cpu_state" and
set "cs_base" or "flags" to STATUS.CRS such that different code would be
generated for each shadow instance. Otherwise, each gpr access would be
indirect. I'm probably missing something here.
Thanks,
Amir
- [PATCH v4 17/33] target/nios2: Prevent writes to read-only or reserved control fields, (continued)
- [PATCH v4 17/33] target/nios2: Prevent writes to read-only or reserved control fields, Richard Henderson, 2022/03/08
- [PATCH v4 13/33] target/nios2: Use hw/registerfields.h for CR_TLBADDR fields, Richard Henderson, 2022/03/08
- [PATCH v4 16/33] target/nios2: Move R_FOO and CR_BAR into enumerations, Richard Henderson, 2022/03/08
- [PATCH v4 24/33] target/nios2: Introduce shadow register sets, Richard Henderson, 2022/03/08
- RE: [PATCH v4 24/33] target/nios2: Introduce shadow register sets,
Amir Gonnen <=
- [PATCH v4 10/33] target/nios2: Clean up nios2_cpu_dump_state, Richard Henderson, 2022/03/08
- [PATCH v4 19/33] target/nios2: Implement CR_STATUS.RSIE, Richard Henderson, 2022/03/08
- [PATCH v4 20/33] target/nios2: Remove CPU_INTERRUPT_NMI, Richard Henderson, 2022/03/08
- [PATCH v4 25/33] target/nios2: Implement rdprs, wrprs, Richard Henderson, 2022/03/08
- [PATCH v4 23/33] target/nios2: Drop CR_STATUS_EH from tb->flags, Richard Henderson, 2022/03/08