diff options
| author | notaz | 2011-09-22 02:11:04 +0300 |
|---|---|---|
| committer | notaz | 2011-09-22 20:32:11 +0300 |
| commit | 9be4ba6483d8d4bbd87fd12ade5c5cc7f9e3f116 (patch) | |
| tree | 5b4d8677556fd541359bcbfa7c127ec8d46c244a /libpcsxcore/new_dynarec/emu_if.h | |
| parent | 174c454a98a71475b72958c9f76293af7d6fb502 (diff) | |
| download | pcsx_rearmed-9be4ba6483d8d4bbd87fd12ade5c5cc7f9e3f116.tar.gz pcsx_rearmed-9be4ba6483d8d4bbd87fd12ade5c5cc7f9e3f116.tar.bz2 pcsx_rearmed-9be4ba6483d8d4bbd87fd12ade5c5cc7f9e3f116.zip | |
drc: do modification check in smaller than page granularity
There are some games that keep writing in the same 4k page where the
code resides (Alien Ressurection is one such example). I've noticed
those accesses are usually to a small region, so keep range of addresses
that has no code and has been recently accessed and check it when the
writes come.
Diffstat (limited to 'libpcsxcore/new_dynarec/emu_if.h')
| -rw-r--r-- | libpcsxcore/new_dynarec/emu_if.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/libpcsxcore/new_dynarec/emu_if.h b/libpcsxcore/new_dynarec/emu_if.h index a561255..128d431 100644 --- a/libpcsxcore/new_dynarec/emu_if.h +++ b/libpcsxcore/new_dynarec/emu_if.h @@ -47,6 +47,9 @@ extern unsigned char byte; extern void *psxH_ptr; +// same as invalid_code, just a region for ram write checks (inclusive) +extern u32 inv_code_start, inv_code_end; + /* cycles/irqs */ extern unsigned int next_interupt; extern int pending_exception; |