The basic premise of hibernate is to copy all information in RAM to HDD and then shutdown, and reload that information back into RAM upon restart.
My question is, when the RAM is repopulated with the stored data from HDD, is all this data placed back into their exact same memory addresses? I'm not sure how the page table would be able to map logical addresses to their physical counterparts otherwise.
...HAH! And you thought it was going to be about how Hibernate saves power, didn't ya.
Seriously though, anyone know how this works?
-
i personally would not think so since renewed caching depends on what app/task has been recalled first after hibernation
cheers ... -
I'd think that the page table could be easily changed on store and restore, just keeping a list of what page is where and so on. But I'd think that it's a bit for bit copy of most every memory page. Check into Linux hibernation... I'll bet they have more documentation on how they do it.
-
Hibernate takes an image of your entire physical memory and writes it to a file. Upon reactivation it writes that file back to memory and resumes.
-
That's basically what he said:
-
Sorry for my ignorance, but why does this matter?
-
Knowledge is power.
-
Just curious. Don't you sometimes look into how things work so you could know how things work?
Argh yeah, although I was hoping for an answer here... -
Linux hibernation may work differently: it typically uses a swap partition instead of a file to write the RAM content on, and I observed it to be slower.
Unfortunately, I cannot answer the question posed by Gator.
Quick Question with respect to Hibernate
Discussion in 'Windows OS and Software' started by Gator, Mar 7, 2007.