All of lore.kernel.org
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Kirkwood: Support basic hotplug for PCI-E
Date: Wed, 21 Nov 2012 12:19:02 -0700	[thread overview]
Message-ID: <20121121191902.GD12822@obsidianresearch.com> (raw)
In-Reply-To: <20121121190230.GB9177@lunn.ch>

On Wed, Nov 21, 2012 at 08:02:30PM +0100, Andrew Lunn wrote:

> I think it may also cause problems with udev persistent rules. The IDs
> will change for devices which are on the second controller and the
> first controller was previously not registered. I've not idea if this
> is just a theoretical problem, or a real problem.

Most udev persistance rules I've seen are based on something more
permanent, like a MAC address or whatnot. The PCI-E bus number is
usually not used because it is historically not stable.

If a system is pluggable then the bus number already changes based on
what ports are plugged, so in a sense this patch makes things a bit
better by providing stable bus numbers.

When the PCI-E driver is integrated with DT it can get a busnr
resource range unique to each port and then the bus numbers will be
stable in almost all cases.

Jason

  reply	other threads:[~2012-11-21 19:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-21 18:25 [PATCH] ARM: Kirkwood: Support basic hotplug for PCI-E Jason Gunthorpe
2012-11-21 18:35 ` Jason Cooper
2012-11-21 18:47   ` Jason Gunthorpe
2012-11-21 18:56     ` Jason Cooper
2012-11-21 19:02   ` Andrew Lunn
2012-11-21 19:19     ` Jason Gunthorpe [this message]
2013-01-07 16:11 ` Jason Cooper

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=20121121191902.GD12822@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.com \
    --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.