This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SNAPSHOT MIPS X86 Memory Alignment
#1
Huh I'm interested in How SNAPSHOT works?
Is it like this ?
SAVE SNAPSHOT-->JPCSP reads all the memory data,packs them,and write them into "Snap_ULJSxxxxxx.bin"
LOAD SNAPSHOT--> JPCSP reads all the data in "Snap_ULJSxxxxxx.bin",unpacks them,and write them into system memory ?

I happened to find some articles about memory alignment of MIPS Architecture (uh...PSP uses MIPS as its processor,uh..i'm not sure about this).

one CSDN user said that he met with strange problems when trying to move (or should i use "transplant" here?) the application,from ARM system to x86 PC system ,later he found that the cause was mem alignment( http://blog.csdn.net/alexxu_118/archive/...px.....i'm sorry it's in Chinese....google"MIPS Memory Alignment" may help)

...both ARM and MIPS request mem alignment...so i wonder whether the same problem occurs when trying to run a PSP\MIPS app on the x86 PC ? and is it the reason why SNAPSHOT doesn't work correctly ?
Reply
#2
The snapshot function performs a full copy of the RAM state, which is already properly aligned.
Your doubt is quite pertinent, and it could be a real case scenario, but the real reason behind why this isn't fully working is because we also have to save the state of Kernel Object Managers (event flags, semaphores, mutexes).
These are all handled inside the emulator and never written to memory, so I'm currently trying to figure out a way to save all this into a file without consuming a massive ammount of space.
The RAM snapshot alone is already about 20MB wide and we still need to add the state of the CPU registers and the state of the Kernel Object Managers. Undecided
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)