| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 09 Jul 2007 14:58:50 +1000 From: Nick Piggin <nickpiggin@...oo.com.au> To: Jeremy Maitin-Shepard <jbms@....edu> CC: Al Boldi <a1426z@...ab.com>, linux-kernel@...r.kernel.org, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: Hibernation Redesign Jeremy Maitin-Shepard wrote: > Nick Piggin <nickpiggin@...oo.com.au> writes: >>Yes, I have a rough idea about how page reclaim works. But I just >>mean it would not be trivial to load the new kernel into physically >>discontiguous memory. Possible of course, but I don't think kexec or >>the setup code could quite cope ATM. > > > It would indeed be a pain for the new kernel to be loaded and have to > use discontiguous memory. The trick is, though, that this is not > necessary. Immediately before jumping to the new kernel, the first X > bytes (where X is the amount of memory the new kernel will get, > typically 16MB or 64MB) of physical memory are backed up into the > arbitrary discontiguous pages that are made available. This will not > take very long, because copying even 64MB of memory is extremely fast. > Then the new kernel is free to use the first X bytes of contiguous > physical memory. Problem solved. Ah, that sounds like it would be the right way to go. Good thinking. -- SUSE Labs, Novell Inc. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists