From: Thomas Gleixner <tglx@linutronix.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <ddaney@caviumnetworks.com>,
Anoop P A <anoop.pa@gmail.com>,
linux-mips@linux-mips.org, LKML <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] Introduce mips_late_time_init
Date: Wed, 8 Dec 2010 22:21:04 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1012082217230.2653@localhost6.localdomain6> (raw)
In-Reply-To: <20101208203704.GB30923@linux-mips.org>
On Wed, 8 Dec 2010, Ralf Baechle wrote:
> Running everything from late_time_init() instead allows the use of kmalloc.
> X86 has the same issue with requiring kmalloc in time_init which is why
> they had moved everything to late_time_init.
It's more ioremap, but yeah.
> So the real question is, why can't we just move the call of time_init()
> in setup_kernel() to where late_time_init() is getting called from for
> all architectures, does anything rely on it getting called early?
That's a good question and I asked it myself already. I can't see a
real reason why something would need it early. Definitely worth to
try.
Thanks,
tglx
next prev parent reply other threads:[~2010-12-08 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1291623812.31822.6.camel@paanoop1-desktop>
[not found] ` <4CFD2095.9040404@caviumnetworks.com>
2010-12-08 20:37 ` [PATCH] Introduce mips_late_time_init Ralf Baechle
2010-12-08 21:21 ` Thomas Gleixner [this message]
2010-12-08 22:45 ` Benjamin Herrenschmidt
2010-12-10 17:21 ` Paul Mundt
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=alpine.LFD.2.00.1012082217230.2653@localhost6.localdomain6 \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=anoop.pa@gmail.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).