linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linas@austin.ibm.com (Linas Vepstas)
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: PCI init vs. memory init
Date: Sat, 29 Apr 2006 17:48:31 +1000	[thread overview]
Message-ID: <17491.6735.199209.247913@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20060428230401.GF22621@austin.ibm.com>

Linas Vepstas writes:

> You mentioned that the sequence of inits seemed wrong, that the 
> PCI init should be done later, after the memory init. I think
> I agree; but when I took a very very quick look at the code, there 
> was no obvious hook in later init to move the PCI init over to. 
> 
> Are you pursuing this further? Should I dig into it?  Any bright
> ideas? Am I missing something obvious?  

I assume you're talking about find_and_init_phbs() and eeh_init(),
which are currently called from pSeries_setup_arch().

Would a core_initcall be early enough for those?  It seems to me that
it probably would be.  What are the actual dependencies?  Clearly it
needs to be before pcibios_init(), which is a subsys_initcall.  Is
there anything else that they need to come before?

> There are several spots in in the powerpc PCI init code where 
> a boot_mem alloc is used instead of kmalloc, and this boot_mem is 
> then hacked around in the case of a PCI hotplug remove.  It would 
> be nice to fix this...

Indeed.

Paul.

      reply	other threads:[~2006-04-29  7:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-28 23:04 PCI init vs. memory init Linas Vepstas
2006-04-29  7:48 ` Paul Mackerras [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=17491.6735.199209.247913@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).