mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Paul Mackerras <paulus@samba.org>
Cc: akpm@osdl.org, johnrose@austin.ibm.com, anton@samba.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2/2] PPC64: RPA dynamic addition/removal of PCI Host Bridges
Date: Wed, 29 Sep 2004 10:48:46 -0700	[thread overview]
Message-ID: <20040929174844.GB12906@kroah.com> (raw)
In-Reply-To: <16730.17837.387665.396256@cargo.ozlabs.ibm.com>

On Wed, Sep 29, 2004 at 03:18:37PM +1000, Paul Mackerras wrote:
> From: John Rose <johnrose@austin.ibm.com>
> 
> The following patch implements the ppc64-specific bits for dynamic (DLPAR)
> addition of PCI Host Bridges.  The entry point for this operation is
> init_phb_dynamic(), which will be called by the RPA DLPAR driver.  
> 
> Among the implementation details, the global number aka PCI domain for the
> newly added PHB is assigned using the same simple counter that assigns it at
> boot.  This has two consequences.  First, the PCI domain associated with a PHB
> will not persist across DLPAR remove and subsequent add.  Second, stress tests
> that repeatedly add/remove PHBs might generate some large values for PCI
> domain.  If we decide at a later point to hash an OF property to PCI domain
> value, this can be easily fixed up.
> 
> Also, the linux,pci-domain property is not generated for the newly added PHBs
> at the moment.  Because there doesn't seem to be an easy way to dynamically add
> single properties to the OFDT, and because the userspace dependency on this
> property is being questioned, I've ignored it for now.  If we decide on a
> solution for this at a later point, it can also be easily fixed up.

Applied, thanks.

greg k-h


      reply	other threads:[~2004-09-29 21:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29  5:18 Paul Mackerras
2004-09-29 17:48 ` Greg KH [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=20040929174844.GB12906@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=anton@samba.org \
    --cc=johnrose@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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

all inboxes | Powered by JetHome®