From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: Clock register in early init
Date: Thu, 24 May 2012 10:02:37 +0900 [thread overview]
Message-ID: <20120524010237.GC11860@linux-sh.org> (raw)
In-Reply-To: <CAJOA=zNic19Eyq-RJpj_pM94wpqY7co0dtKu1O+27B-wZMm=MA@mail.gmail.com>
On Tue, May 22, 2012 at 10:37:15AM -0700, Turquette, Mike wrote:
> On Tue, May 22, 2012 at 5:08 AM, Peter De Schrijver
> <pdeschrijver@nvidia.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?
>
This is what sh does for its asm/clkdev.h __clkdev_alloc(), which is
really the only difference over the ARM version. It always seemed a bit
silly to me to make early allocation an arch-specific property.
WARNING: multiple messages have this Message-ID (diff)
From: Paul Mundt <lethal@linux-sh.org>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: Peter De Schrijver <pdeschrijver@nvidia.com>,
Ben Dooks <ben.dooks@codethink.co.uk>,
Prashant Gaikwad <pgaikwad@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Clock register in early init
Date: Thu, 24 May 2012 10:02:37 +0900 [thread overview]
Message-ID: <20120524010237.GC11860@linux-sh.org> (raw)
In-Reply-To: <CAJOA=zNic19Eyq-RJpj_pM94wpqY7co0dtKu1O+27B-wZMm=MA@mail.gmail.com>
On Tue, May 22, 2012 at 10:37:15AM -0700, Turquette, Mike wrote:
> On Tue, May 22, 2012 at 5:08 AM, Peter De Schrijver
> <pdeschrijver@nvidia.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?
>
This is what sh does for its asm/clkdev.h __clkdev_alloc(), which is
really the only difference over the ARM version. It always seemed a bit
silly to me to make early allocation an arch-specific property.
next prev parent reply other threads:[~2012-05-24 1:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1337227884.2066.9.camel@pgaikwad-dt2>
[not found] ` <20120517062131.GA9305@gmail.com>
2012-05-18 4:48 ` Clock register in early init Prashant Gaikwad
2012-05-18 4:48 ` Prashant Gaikwad
2012-05-18 11:21 ` Peter De Schrijver
2012-05-18 11:21 ` Peter De Schrijver
2012-05-18 20:17 ` Turquette, Mike
2012-05-18 20:17 ` Turquette, Mike
2012-05-21 8:46 ` Peter De Schrijver
2012-05-21 8:46 ` Peter De Schrijver
2012-05-21 18:05 ` Turquette, Mike
2012-05-21 18:05 ` Turquette, Mike
2012-05-22 11:15 ` Peter De Schrijver
2012-05-22 11:15 ` Peter De Schrijver
2012-05-22 9:20 ` Ben Dooks
2012-05-22 9:20 ` Ben Dooks
2012-05-22 12:08 ` Peter De Schrijver
2012-05-22 12:08 ` Peter De Schrijver
2012-05-22 17:37 ` Turquette, Mike
2012-05-22 17:37 ` Turquette, Mike
2012-05-23 9:19 ` Peter De Schrijver
2012-05-23 9:19 ` Peter De Schrijver
2012-05-23 16:20 ` Turquette, Mike
2012-05-23 16:20 ` Turquette, Mike
2012-05-24 1:02 ` Paul Mundt [this message]
2012-05-24 1:02 ` Paul Mundt
2012-05-24 15:51 ` Turquette, Mike
2012-05-24 15:51 ` Turquette, Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120524010237.GC11860@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.