public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@debian.org>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Matthew Wilcox <willy@debian.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [3/3] PCI segment support
Date: Tue, 8 Apr 2003 17:50:26 +0100	[thread overview]
Message-ID: <20030408165026.GA23430@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20030408203824.A27019@jurassic.park.msu.ru>

On Tue, Apr 08, 2003 at 08:38:24PM +0400, Ivan Kokshaysky wrote:
> On Tue, Apr 08, 2003 at 12:44:11AM +0100, Matthew Wilcox wrote:
> >  - Add segment to pci_bus.
> >  - Change the sysfs name of each device to include a 16-bit segment ID.
> 
> First of all, the "segment" name is extremely misleading. PCI spec
> assumes everywhere that "segment" is a group of devices sitting
> on the same wires (ie primary and secondary buses of the PCI-to-PCI
> bridge are *different* segments).

I don't mind changing it to `domain', I prefer the term myself.
ACPI calls it `_SEG' so I went with segment.

> Second, why not
> 
> -	strcpy(dev->dev.bus_id,dev->slot_name);
> +	sprintf(dev->dev.bus_id, "%04x:%s", pci_controller_num(dev),
> +		dev->slot_name);
> 
> ?

Because it's possible to have multiple pci root bridges in the same
pci domain.  This is true on at least HP's ia64 & parisc boxes.

-- 
"It's not Hollywood.  War is real, war is primarily not about defeat or
victory, it is about death.  I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk

  reply	other threads:[~2003-04-08 16:38 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 23:44 [PATCH] [3/3] PCI segment support Matthew Wilcox
2003-04-08 16:38 ` Ivan Kokshaysky
2003-04-08 16:50   ` Matthew Wilcox [this message]
2003-04-08 17:21     ` Ivan Kokshaysky
2003-04-08 17:31       ` Matthew Wilcox
2003-04-09  5:41         ` Grant Grundler
2003-06-08 16:43   ` Matthew Wilcox
2003-06-08 21:33     ` Russell King
2003-06-08 23:16       ` Alan Cox
2003-06-09 10:07     ` Ivan Kokshaysky
2003-06-09 10:20       ` David S. Miller
2003-06-09 10:42         ` Ivan Kokshaysky
2003-06-09 10:43           ` David S. Miller
2003-06-09 11:00             ` Ivan Kokshaysky
2003-06-09 11:04               ` David S. Miller
2003-06-09 11:17       ` Matthew Wilcox
2003-06-09 11:26         ` Ivan Kokshaysky
2003-06-09 14:34           ` Matthew Wilcox
2003-06-09 11:41         ` Ivan Kokshaysky

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=20030408165026.GA23430@parcelfarce.linux.theplanet.co.uk \
    --to=willy@debian.org \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.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