From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Mark McLoughlin <markmc@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] x86: call early_cpu_init at the same point
Date: Mon, 28 Jul 2008 17:08:44 +0200 [thread overview]
Message-ID: <20080728150844.GD32111@elte.hu> (raw)
In-Reply-To: <4888A410.3020108@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Ingo Molnar wrote:
>> * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>>
>>
>>> Call early_cpu_init() at the same (early) point in setup_arch(). The
>>> x86_64 code was calling it relatively late, after when other arch
>>> code need to do cpu-related setup which depends on it.
>>>
>>
>> applied to tip/x86/urgent, thanks Jeremy.
>
> Thanks. Curious to see if this causes any breakage, especially in
> numa-ish type systems.
no badness so far.
Ingo
prev parent reply other threads:[~2008-07-28 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 23:49 [PATCH 1/2] x86: call early_cpu_init at the same point Jeremy Fitzhardinge
2008-07-24 10:28 ` Ingo Molnar
2008-07-24 15:47 ` Jeremy Fitzhardinge
2008-07-28 15:08 ` Ingo Molnar [this message]
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=20080728150844.GD32111@elte.hu \
--to=mingo@elte.hu \
--cc=ehabkost@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markmc@redhat.com \
/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