| 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: <CAJOA=zNic19Eyq-RJpj_pM94wpqY7co0dtKu1O+27B-wZMm=MA@mail.gmail.com> Date: Tue, 22 May 2012 10:37:15 -0700 From: "Turquette, Mike" <mturquette@...com> To: Peter De Schrijver <pdeschrijver@...dia.com> Cc: Ben Dooks <ben.dooks@...ethink.co.uk>, Prashant Gaikwad <pgaikwad@...dia.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: Clock register in early init On Tue, May 22, 2012 at 5:08 AM, Peter De Schrijver <pdeschrijver@...dia.com> wrote: >> We had at-least that on the older Samsung parts and they where still >> growing. I would suggest that in a multi-kernel image situation the >> more data that can be discarded after init-time the better. >> >> Also, __initdata gets gathered into one place so there's no possibility >> of page fragmentation there. If you mean fragmentation of the memory >> map, then allocate the size of all the clocks you know of at init time >> in one go. >> > > That would work, except that clocks are needed before kmalloc is available. > Is static initialization the only way to solve this problem? What about using the bootmem allocator for early init clocks? Regards, Mike > Cheers, > > Peter. -- 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