public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [Pcihpd-discuss] PCI hotplug broken on IA64
Date: Thu, 31 Oct 2002 05:58:00 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805305@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805303@msgid-missing>

On Wed, Oct 30, 2002 at 06:00:40PM -0800, KOCHI, Takayoshi wrote:
> Hi,
> 
> The PCI segment support which was introduced at 2.4.19-020821 ia64 patch
> broke PCI hotplug core driver.  The way ia64 port does is using
> ia64 specific 'pci_controller' structure, embedding a segment
> number in it and making pci_bus->sysdata point to the structure.

Yes, Chris McDermott just sent me a patch much like this one a few days
ago.

> All config space access functions refer to the structure so if
> pci_controller structures are not setup correctly, all pci
> configuration space acesss will fail.
> 
> I don't think the current way of accessing PCI configuration space
> with temporary pci_dev and pci_bus is definitive answer but we
> are depending on it now.
> 
> Could someone enlighten me?
> Any ideas?

The correct thing to do is do what we did in 2.5.  There is no more
*_nodev functions, as we changed the pci_ops structure.  Even when
segment support goes into 2.5, the pci hotplug code should not care at
all.

That being said, I don't think the huge pci_ops change would be a good
thing to do right now in 2.4.  I also do not want to be forced to add
the segment value to the *_nodev functions, as that is just getting too
messy.

Maybe a backport of the pci_ops changes is the best thing to do...

Any other ideas?

thanks,

greg k-h


  parent reply	other threads:[~2002-10-31  5:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  4:49 [Linux-ia64] RE: [Pcihpd-discuss] PCI hotplug broken on IA64 Lee, Jung-Ik
2002-10-31  5:52 ` [Linux-ia64] " Greg KH
2002-10-31  5:58 ` Greg KH [this message]
2002-10-31  6:00 ` Greg KH
2002-10-31  6:55 ` [Linux-ia64] " Lee, Jung-Ik
2002-10-31  7:40 ` [Linux-ia64] " Greg KH
2002-10-31  8:03 ` Scott Murray
2002-10-31  8:19 ` Greg KH
2002-10-31  8:41 ` Scott Murray
2002-10-31 12:27 ` Matthew Wilcox

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=marc-linux-ia64-105590709805305@msgid-missing \
    --to=greg@kroah.com \
    --cc=linux-ia64@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