From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yinghai@kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] x86/pci: try to detect host_bridge pci_cfg_space
Date: Sun, 08 Mar 2009 14:05:16 -0700 [thread overview]
Message-ID: <49B4330C.1060700@zytor.com> (raw)
In-Reply-To: <20090308145803.GL25995@parisc-linux.org>
Matthew Wilcox wrote:
> On Sun, Mar 08, 2009 at 12:04:37PM +0100, Ingo Molnar wrote:
>> I'd also suggest to flip around the subject line from x86/pci to
>> pci/x86 - it's more of a PCI patch than a pure x86 patch. The
>> same problem could affect other platforms too i suspect.
>
> Not all platforms expose the root bridge in PCI configuration space.
> Intel ia64 platforms do have a materialised root bridge; HP's don't.
> (I don't know whether Intel ship any PCIe ia64 machines or not). I
> don't remember details for other platforms, but I think Intel is the odd
> one out in this regard.
>
It's still generic PCI code, however. If there is no host bridge
exposed in PCI space, the patch is a noop.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-03-08 21:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 0:51 [PATCH] x86/pci: try to detect host_bridge pci_cfg_space Yinghai Lu
2009-03-07 0:58 ` H. Peter Anvin
2009-03-07 1:03 ` Yinghai Lu
2009-03-07 1:08 ` H. Peter Anvin
2009-03-07 1:11 ` Yinghai Lu
2009-03-07 1:04 ` H. Peter Anvin
2009-03-07 1:07 ` Yinghai Lu
2009-03-08 11:04 ` Ingo Molnar
2009-03-08 14:58 ` Matthew Wilcox
2009-03-08 21:05 ` H. Peter Anvin [this message]
2009-03-08 21:10 ` Yinghai Lu
2009-03-08 21:15 ` H. Peter Anvin
2009-03-08 21:21 ` Yinghai Lu
2009-03-08 21:31 ` Ingo Molnar
2009-03-08 22:01 ` Matthew Wilcox
2009-03-08 22:06 ` H. Peter Anvin
2009-03-08 22:28 ` Ingo Molnar
2009-03-08 23:00 ` Yinghai Lu
2009-03-09 4:35 ` [PATCH] pci/x86: try to detect host_bridge pci_cfg_space -v2 Yinghai Lu
2009-03-20 2:02 ` Jesse Barnes
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=49B4330C.1060700@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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