| 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
| ||
|
Message-Id: <20120313.011633.151968036751263435.davem@davemloft.net> Date: Tue, 13 Mar 2012 01:16:33 -0700 (PDT) From: David Miller <davem@...emloft.net> To: apenwarr@...il.com Cc: akpm@...ux-foundation.org, josh@...htriplett.org, paulmck@...ux.vnet.ibm.com, mingo@...e.hu, a.p.zijlstra@...llo.nl, fdinitto@...hat.com, hannes@...xchg.org, olaf@...fle.de, paul.gortmaker@...driver.com, tj@...nel.org, hpa@...ux.intel.com, yinghai@...nel.org, linux-kernel@...r.kernel.org, linux-mm@...ck.org Subject: Re: [PATCH 0/5] Persist printk buffer across reboots. From: Avery Pennarun <apenwarr@...il.com> Date: Tue, 13 Mar 2012 04:10:42 -0400 > On Tue, Mar 13, 2012 at 3:18 AM, David Miller <davem@...emloft.net> wrote: >> I'm only saying that you should design your stuff such that an >> architecture with such features could easily hook into it using this >> kind facility. > > How about this? Function signature looks good. But on a platform with firmware based memory retaining facilitites we're going to need to invoke this way before bootmem or memblocks are even setup, because the retain call influences the free memory lists that the firmware gives to us and those free memory lists are what we use to populate the memblock tables. -- 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