From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH] x86/PCI: don't fall back to defaults if _CRS has no apertures
Date: Fri, 27 Jan 2012 09:34:46 -0800 [thread overview]
Message-ID: <20120127093446.23955111@jbarnes-desktop> (raw)
In-Reply-To: <20120118004121.1089.43631.stgit@bhelgaas.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Tue, 17 Jan 2012 17:41:21 -0700
Bjorn Helgaas <bhelgaas@google.com> wrote:
> Host bridges that lead to things like the Uncore need not have any
> I/O port or MMIO apertures. For example, in this case:
>
> ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
> PCI: root bus ff: using default resources
> PCI host bridge to bus 0000:ff
> pci_bus 0000:ff: root bus resource [io 0x0000-0xffff]
> pci_bus 0000:ff: root bus resource [mem 0x00000000-0x3fffffffffff]
>
> we should not pretend those default resources are available on bus ff.
Applied to -next, let's see if this _CRS change breaks anything. :)
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-01-27 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 0:41 [PATCH] allow host bridges with no io/mem apertures Bjorn Helgaas
2012-01-18 0:41 ` [PATCH] x86/PCI: don't fall back to defaults if _CRS has no apertures Bjorn Helgaas
2012-01-18 4:09 ` Yinghai Lu
2012-01-18 4:29 ` Bjorn Helgaas
2012-01-27 17:34 ` Jesse Barnes [this message]
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=20120127093446.23955111@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--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