From: Robert Hancock <hancockr@shaw.ca>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH -mm] 0/2: PCI MMCONFIG-related updates
Date: Wed, 30 May 2007 17:31:52 -0600 [thread overview]
Message-ID: <465E0968.90707@shaw.ca> (raw)
In-Reply-To: <200705300821.11555.jbarnes@virtuousgeek.org>
Jesse Barnes wrote:
> On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
>> These two patches implement some changes in behavior related to PCI
>> MMCONFIG configuration space access. One changes the way in which we
>> validate the MCFG table provided by the BIOS by checking it against
>> ACPI motherboard resources instead of the E820 table. The BIOS is not
>> required to reserve this area in the E820 table, so checking that
>> results in MMCONFIG being unnecessarily disabled on some machines.
>>
>> Some Intel chipsets where MMCONFIG was being disabled previously
>> (but won't be with the first patch) had problems, not due to the
>> MCFG table being broken, but because the access was hosed by the way
>> in which we do PCI BAR sizing. The second patch fixes this problem.
>>
>> This is requested for inclusion in the -mm tree for testing.
>
> Robert, should we also pull in the 915 and 965 chipset specific register
> poking code? It might be a good sanity check against ACPI (i.e. if ACPI and
> the actual register window disagree, we can assume the BIOS is broken and
> MCFG is not safe to use). If so, I'll update and repost them against your
> patchset.
Probably not a bad idea..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
prev parent reply other threads:[~2007-05-30 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:01 [PATCH -mm] 0/2: PCI MMCONFIG-related updates Robert Hancock
2007-05-30 15:21 ` Jesse Barnes
2007-05-30 23:31 ` Robert Hancock [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=465E0968.90707@shaw.ca \
--to=hancockr@shaw.ca \
--cc=akpm@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox