| [hatari-devel] Hatari and OUTSIDE (virtual memory manager) |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] Hatari and OUTSIDE (virtual memory manager)
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Tue, 2 Oct 2018 12:01:17 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1538474477; s=strato-dkim-0002; d=seimet.de; h=Message-ID:Subject:To:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH:From: Subject:Sender; bh=rcS9kFsx0tjcAw0btGsJzCcPuMzZv5XUX3J69A38hQ0=; b=URfo+kSgf4Vh/MfVBLdNd0SNB+fQmG2HEnqW4t3un3iMFK7SrPfirT/ouv+kpWQMEB O35sWIIFJPbFBIkykaJ06rVBH+wsQ1PSve3EJwvvmVMFj37V/yepAhzsmxNtVamT3vuw 4+LxsOqalNtx1mKis4BY3lsZmUiLdiql3Fp1dKx28tE5129qcb0ZB0YgjJ5oZeO/4te4 nf+ci6GQT1HFzapeM2sY6gq7AVW9kPHsCVv8Ylzxb7ePgA/QuxgrnfFj9BeuC7lPp2Gb QDdVnXKBi5ic36uVxEZYGo5OFBgh1dfJaukQpE1QB/4dyQL+dTlcoLeT1hwwUoTnJE/x bvIg==
Hi,
In order to test Hatari's behavior wrt PMMU and other options a bit, I
tried to start OUTSIDE. This one definitely uses the PMMU :-).
Hatari crashes with a segmentation fault when running OUTSIDE:
#0 0x0000000000000002 in ?? ()
#1 0x0000000000000002 in ?? ()
#2 0x0000555555e900f1 in put_byte_mmu030c_state (v=50, addr=1744437248)
at /home/us/hatari/hatari/src/cpu/cpummu030.h:588
#3 op_08a8_35_ff (opcode=<optimized out>)
at /home/us/hatari/hatari/src/cpu/cpuemu_35.c:4589
#4 0x0000555555936d15 in m68k_run_mmu030 ()
at /home/us/hatari/hatari/src/cpu/newcpu.c:6602
#5 0x0000555555931c8a in m68k_go (may_quit=<optimized out>)
at /home/us/hatari/hatari/src/cpu/newcpu.c:7698
PMMU emulation, cycle exact and prefetch mode were selected. Everything
else was configured just like you find it to the Hatari configuration I
attached to my posting in the NVDI thread.
If somebody is interested in investigating this, just download OUTSIDE from
http://www.seimet.de/atari/en/index.html. There is a German manual only,
but the basic installation is simple:
1. Put OUTSIDE.PRG into the AUTO folder
2. Launch OUTCONF.APP
3. Select the swap partition. This partition will be write selected
while OUTSIDE is running. Only non-allocated clusters will be used for
swapping. I recommend an empty partition.
4. Reboot
5. You should now have (additional, depending on the settings) alternate RAM.
Note that the OUTSIDE archive also contains the source code. For testing
the PMMU it's probably a good candidate. You can also configure 16 and
32 KB pages to be used, not just the usual 8 KB pages. Both TT and
Falcon are supported.
Best regards
Uwe