From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH -mm] 1/2: MMCONFIG: validate against ACPI motherboard resources
Date: Mon, 4 Jun 2007 08:37:10 -0700 [thread overview]
Message-ID: <200706040837.10720.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20070604121250.GA33621@dspnet.fr.eu.org>
On Monday, June 4, 2007 5:12:50 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.
I'm not sure what you're objecting to? Are you suggesting that we use
mmconfig space as defined by the bridge register even if it's not mentioned
(or doesn't match) the MCFG table?
Jesse
prev parent reply other threads:[~2007-06-04 15:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:03 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
2007-06-04 15:37 ` 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=200706040837.10720.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@linux-foundation.org \
--cc=galibert@pobox.com \
--cc=hancockr@shaw.ca \
--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
all inboxes | Powered by JetHome®