Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753048Ab2EVRhi (ORCPT ); Tue, 22 May 2012 13:37:38 -0400 Received: from na3sys009aog126.obsmtp.com ([74.125.149.155]:52360 "EHLO na3sys009aog126.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751298Ab2EVRhh (ORCPT ); Tue, 22 May 2012 13:37:37 -0400 MIME-Version: 1.0 In-Reply-To: <20120522120851.GI8730@tbergstrom-lnx.Nvidia.com> References: <1337227884.2066.9.camel@pgaikwad-dt2> <20120517062131.GA9305@gmail.com> <1337316517.22560.19.camel@pgaikwad-dt2> <20120518112104.GL20304@tbergstrom-lnx.Nvidia.com> <20120521084642.GV20304@tbergstrom-lnx.Nvidia.com> <4FBB5A72.2080101@codethink.co.uk> <20120522120851.GI8730@tbergstrom-lnx.Nvidia.com> From: "Turquette, Mike" Date: Tue, 22 May 2012 10:37:15 -0700 Message-ID: Subject: Re: Clock register in early init To: Peter De Schrijver Cc: Ben Dooks , Prashant Gaikwad , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1021 Lines: 29 On Tue, May 22, 2012 at 5:08 AM, Peter De Schrijver 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/