| 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:45:35 +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: >>This is the Morton method, isn't it? :) I remember it sounding like a >>very good idea when he brought it up, but I can't remember the details >>of why it was rejected or what the problems were. > > > Perhaps he did bring it up before I did. Please forward me a link to > the thread or other reference if you can find it, as I'd be interested > in reading it. Sent in the next mail. >>I suspect that freeing memory on the fly for the new kernel >>would be non-trivial (but possible), however simply having a reserve >>RAM region for the new kernel would be fine for a first step. > > > Freeing memory on the fly should be extremely easy for the kernel (this > is precisely what it does when it needs to satisfy an allocation). Note > that the memory allocated need not be contiguous. 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. -- 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