public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: rajesh.shah@intel.com
Cc: ak@suse.de, gregkh@suse.de, akpm@osdl.org, brice@myri.com,
	76306.1226@compuserve.com, arjan@linux.intel.com,
	linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/2] PCI: improve extended config space verification
Date: Fri, 23 Jun 2006 16:18:19 -0400	[thread overview]
Message-ID: <449C4C8B.4010009@garzik.org> (raw)
In-Reply-To: <20060623200928.036235000@rshah1-sfield.jf.intel.com>

rajesh.shah@intel.com wrote:
> ACPI defines an MCFG table that gives us the pointer to where the
> extended PCI-X/PCI-Express configuration space exists. We validate
> this region today by making sure that the reported range is marked
> as reserved in the int 15 E820 memory map. However, the PCI firmware
> spec states this is optional and BIOS should be reporting the MCFG
> range as a motherboard resources. Several of my systems failed the
> existing check and ended up without extended PCI-Express config
> space. This patch extends the verification to also look for the
> MCFG range as a motherboard resource in ACPI. This solves the
> problem on my i386 as well as x86_64 test systems.

On a related note -- PCI segments potentially enumerated in ACPI -- I 
have a PCI segments patch available at:

'pciseg' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git

GregKH also has a few fixes for this which I need to integrate, too.

	Jeff



      parent reply	other threads:[~2006-06-23 20:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-23 20:09 [patch 0/2] PCI: improve extended config space verification rajesh.shah
2006-06-23 20:09 ` [patch 1/2] i386 " rajesh.shah
2006-06-23 20:09 ` [patch 2/2] x86_64 " rajesh.shah
2006-06-23 20:30   ` Andi Kleen
2006-06-23 22:43     ` Greg KH
2006-06-27  0:57       ` Rajesh Shah
2006-06-23 20:18 ` Jeff Garzik [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=449C4C8B.4010009@garzik.org \
    --to=jeff@garzik.org \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@linux.intel.com \
    --cc=brice@myri.com \
    --cc=gregkh@suse.de \
    --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