public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Jiang Liu <jiang.liu@huawei.com>, Tony Luck <tony.luck@intel.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Taku Izumi <izumi.taku@jp.fujitsu.com>,
	Toshi Kani <toshi.kani@hp.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-pci@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/22] PCI: Iterate pci host bridge instead of pci root bus
Date: Wed, 6 Feb 2013 06:53:40 -0200	[thread overview]
Message-ID: <20130206065340.416a708b@redhat.com> (raw)
In-Reply-To: <CAE9FiQWvmK7N2z19B9ZiMyc_T6cJdpWoWr3mExpuwUA4ogBc3w@mail.gmail.com>

Em Tue, 5 Feb 2013 16:47:10 -0800
Yinghai Lu <yinghai@kernel.org> escreveu:

> On Tue, Feb 5, 2013 at 4:19 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> >
> > Maybe.  I'd rather not introduce for_each_pci_host_bridge() at all, if
> > we can avoid it.  Every place it's used is a place we have to audit to
> > make sure it's safe.  I think your audit above is correct and
> > complete, but it relies on way too much architecture knowledge.  It's
> > better if we can deduce correctness without knowing which arches
> > support hotplug and which CPUs support EDAC.
> >
> > As soon as for_each_pci_host_bridge() is in the tree, those uses can
> > be copied to even more places.  It's a macro, so it's usable by any
> > module, even out-of-tree ones that we'll never see and can't fix.  So
> > we won't really have a good way to deprecate and remove it.
> 
> Now we only have two references in modules.
> 
> drivers/edac/i7core_edac.c:     for_each_pci_host_bridge(host_bridge) {
> drivers/pci/hotplug/sgi_hotplug.c:      for_each_pci_host_bridge(host_bridge) {
> 
> for the sgi_hotplug.c, it should be same problem that have for acpiphp
> and pciehp.
> need to make it support pci host bridge hotplug anyway.
> 
> for edac, we need to check Mauro about their plan.

The i7core_pci_lastbus() code at i7core_edac is there to make it work
with some Nehalem/Nehalem-EP machines that hide the memory controller's
PCI ID by using an artificially low last bus. There's no plan to
support Nehalem-EX, as the information I got is that there's no way
to access the memory controller registers on it without interfering with
BIOS.

It should be noticed, however, that I got a report of a Sandy Bridge
server that is also hiding the memory controller's PCI address.
So, maybe we'll need to add later some logic at sb_edac to unhide the
memory controller, just like the one in i7core_edac.

> 
> After those two are addressed, we can drop that EXPORT_SYMBOL_GPL for
> pci_get_next_host_bridge.
> 
> We do have pci_get_domain_bus_and_slot() as export symbol.
> So we export pci_get_next_host_bridge should be ok now.
> and it would be better than export root buses list.
> 
> Thanks
> 
> Yinghai


-- 

Cheers,
Mauro

  reply	other threads:[~2013-02-06  8:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAE9FiQXHG01NjnYNDbC-KEpbcvY-q4pBe97CxTOGS7W4vZQBYQ@mail.gmail.com>
     [not found] ` <1359314629-18651-1-git-send-email-yinghai@kernel.org>
     [not found]   ` <CAErSpo6r_LNEtYB3j5ELb8NdHu0a6_YOVj8S32CmByGFUpSsbg@mail.gmail.com>
2013-02-03  5:05     ` [PATCH v3 00/22] PCI: Iterate pci host bridge instead of pci root bus Yinghai Lu
2013-02-05 23:55       ` Yinghai Lu
2013-02-06  0:19         ` Bjorn Helgaas
2013-02-06  0:47           ` Yinghai Lu
2013-02-06  8:53             ` Mauro Carvalho Chehab [this message]
2013-02-06 17:45               ` Bjorn Helgaas
2013-02-07 10:24                 ` Mauro Carvalho Chehab
2013-02-06 17:54             ` Bjorn Helgaas
2013-02-06 18:59               ` Yinghai Lu
2013-02-06 20:50                 ` Bjorn Helgaas
2013-02-06 21:28                   ` Yinghai Lu
2013-02-06 21:43                     ` Rafael J. Wysocki
2013-02-06 21:53                       ` Yinghai Lu
2013-02-06 22:05                         ` Rafael J. Wysocki
2013-02-06 23:02                           ` Bjorn Helgaas
2013-02-06 23:31                             ` Yinghai Lu
2013-02-07  0:27                             ` Jiang Liu

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=20130206065340.416a708b@redhat.com \
    --to=mchehab@redhat.com \
    --cc=bhelgaas@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=jiang.liu@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=rjw@sisk.pl \
    --cc=tony.luck@intel.com \
    --cc=toshi.kani@hp.com \
    --cc=yinghai@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