All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: William Lee Irwin III <wli@holomorphy.com>,
	"Martin J. Bligh" <mbligh@aracnet.com>,
	Matthew Dobson <colpatch@us.ibm.com>,
	linux-kernel@vger.kernel.org, hohnbaum@us.ibm.com,
	mochel@osdl.org
Subject: Re: [0/4] NUMA-Q: remove PCI bus number mangling
Date: Tue, 12 Nov 2002 16:20:32 -0800	[thread overview]
Message-ID: <20021113002032.GF32274@kroah.com> (raw)
In-Reply-To: <20021113001246.GC23425@holomorphy.com>

On Tue, Nov 12, 2002 at 04:12:46PM -0800, William Lee Irwin III wrote:
> On Tue, Nov 12, 2002 at 03:58:24PM -0800, William Lee Irwin III wrote:
> >> Okay, an attempt to remedy this world-breaking braindamage with the
> >> fewest lines of code:
> >> This alters PCI bus number "clash" detection to compare ->sysdata in
> >> addition to the numbers. The bus number is not a unique identifier.
> 
> On Tue, Nov 12, 2002 at 04:04:35PM -0800, Greg KH wrote:
> > Um, why not?
> > And what would /sys/bus/pci/devices look like if you allow the same
> > identifiers for different devices?  :)
> > thanks,
> > greg k-h
> 
> (1) incorrect semantics:
> 	multiple domains/segments exist, and the bus number is not
> 	qualified with such
> (2) insufficient cardinality:
> 	even in the presence of remapping schemes the bus space is limited
> 	to less than the number of buses requiring unique identifiers

Ok, then also please fix up drivers/pci/probe.c::pci_setup_device() to
set a unique slot_name up for the pci_dev, if you have multiple
domains/segments.

thanks,

greg k-h

  reply	other threads:[~2002-11-13  0:19 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 12:37 [0/4] NUMA-Q: remove PCI bus number mangling William Lee Irwin III
2002-11-12 20:52 ` William Lee Irwin III
2002-11-12 20:55   ` William Lee Irwin III
2002-11-12 21:29   ` Matthew Dobson
2002-11-12 21:35     ` William Lee Irwin III
2002-11-12 21:39       ` William Lee Irwin III
2002-11-12 22:46         ` Martin J. Bligh
2002-11-12 21:53           ` William Lee Irwin III
2002-11-12 23:53             ` Martin J. Bligh
2002-11-12 22:59               ` William Lee Irwin III
2002-11-12 23:19                 ` William Lee Irwin III
2002-11-12 23:58                 ` William Lee Irwin III
2002-11-13  0:04                   ` Greg KH
2002-11-13  0:12                     ` William Lee Irwin III
2002-11-13  0:20                       ` Greg KH [this message]
2002-11-13  0:28                         ` William Lee Irwin III
2002-11-13  1:01                           ` William Lee Irwin III
2002-11-13 12:07                           ` Ivan Kokshaysky
2002-11-13 20:59                             ` William Lee Irwin III
2002-11-13 10:10                         ` William Lee Irwin III
2002-11-13 11:20                           ` William Lee Irwin III
2003-01-01  9:28                             ` William Lee Irwin III
2002-11-12 21:48       ` William Lee Irwin III
2002-11-12 21:48       ` William Lee Irwin III
2002-11-12 20:53 ` William Lee Irwin III

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=20021113002032.GF32274@kroah.com \
    --to=greg@kroah.com \
    --cc=colpatch@us.ibm.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=mochel@osdl.org \
    --cc=wli@holomorphy.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 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.