From: Robert Hancock <hancockr@shaw.ca>
To: Olivier Galibert <galibert@pobox.com>,
Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH -mm] 1/2: MMCONFIG: validate against ACPI motherboard resources
Date: Mon, 04 Jun 2007 08:35:06 -0600 [thread overview]
Message-ID: <4664231A.2040703@shaw.ca> (raw)
In-Reply-To: <20070604121250.GA33621@dspnet.fr.eu.org>
Olivier Galibert wrote:
> On Tue, May 29, 2007 at 10:03:32PM -0600, Robert Hancock wrote:
>> -Validate that the area is reserved even if we read it from the
>> chipset directly and not from the MCFG table. This catches the case
>> where the BIOS didn't set the location properly in the chipset and
>> has mapped it over other things it shouldn't have.
>
> Just for the record, I still fundamentally disagree with that part.
> You're not catching what you think you're catching, since the chipset
> tells you what it is going to decode as mmconfig, no matter what is
> connected to it.
But we don't - not in the case where it's overlapped some other area
with the MMCONFIG region. We saw a case of this on some of the Intel
boards, where the MMCONFIG is a 128MB area at 0xf0000000, and when
sizing the BARs on a PCI Express video device with a 256MB region, it
ended up being located momentarily at f0000000-ffffffff, which
overlapped the MMCONFIG area. That caused MMCONFIG to stop working, so
apparently on that chipset, PCI Express devices connected to the
northbridge have a higher decode priority than the MMCONFIG area.
If the BIOS is so screwed up that this becomes an issue, I don't think
we can sanely try to use the table, since we can't anticipate all the
potential problems that might result.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2007-06-04 14:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:03 [PATCH -mm] 1/2: MMCONFIG: validate against ACPI motherboard resources Robert Hancock
2007-05-30 4:45 ` Linus Torvalds
2007-05-30 8:41 ` Matt Keenan
2007-05-30 14:35 ` Robert Hancock
2007-05-30 15:05 ` Linus Torvalds
2007-05-30 15:38 ` Mark Lord
2007-05-30 23:33 ` Robert Hancock
2007-05-30 17:23 ` Dave Jones
2007-05-30 17:37 ` Linus Torvalds
2007-05-30 17:54 ` Dave Jones
2007-05-30 17:40 ` Andrew Morton
2007-05-31 1:02 ` Robert Hancock
2007-06-04 12:12 ` Olivier Galibert
2007-06-04 14:35 ` Robert Hancock [this message]
2007-06-04 15:37 ` 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=4664231A.2040703@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--cc=galibert@pobox.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.