public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
	Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
	"Brown, Len" <len.brown@intel.com>,
	Rajesh Shah <rajesh.shah@intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [patch, take 3] PCI: use ACPI to verify extended config space on x86
Date: Fri, 14 Jul 2006 16:15:41 +0200	[thread overview]
Message-ID: <200607141615.41338.ak@suse.de> (raw)
In-Reply-To: <200607141000_MC3-1-C4FF-945F@compuserve.com>

On Friday 14 July 2006 15:57, Chuck Ebbert wrote:
> In-Reply-To: <1152869988.3159.25.camel@laptopd505.fenrus.org>
> 
> On Fri, 14 Jul 2006 11:39:48 +0200, Arjan van de Ven wrote:
> 
> > > Extend the verification for PCI-X/PCI-Express extended config
> > > space pointer. Checks whether the MCFG address range is listed
> > > as a motherboard resource, per the PCI firmware spec.
> > 
> > I'm still not quite happy about this; the entire point of the check is
> > that we CAN'T trust the ACPI implementation, and want a second opinion.
> > This patch basically asks the ACPI implementation if we can trust the
> > ACPI implementation. I'm not sure that's a good idea.
> > And I understood that most issues went away with the more relaxed check
> > that is in gregkh's tree already (if not in mainline, I should check
> > that). 
> 
> The more-relaxed check is in mainline.  I wrote it, but it didn't even
> fix the problem on my own machine. 

Why did you submit it then when it didn't work?

> This did. 
> 
> According to Rajesh, the spec doesn't require the MCFG space to be
> e820-reserved, so that's not really a valid check.

Anyways Rajesh's patch is probably the way to go. If the ACPI
implementatin is self consistent it can be probably trusted.

The e820 check was just a heuristic and it clearly wasn't a good one. 

-Andi
 

  reply	other threads:[~2006-07-14 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-14 13:57 [patch, take 3] PCI: use ACPI to verify extended config space on x86 Chuck Ebbert
2006-07-14 14:15 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14  7:34 Chuck Ebbert
2006-07-14  9:39 ` Arjan van de Ven

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=200607141615.41338.ak@suse.de \
    --to=ak@suse.de \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=rajesh.shah@intel.com \
    /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