public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andi Kleen <ak@suse.de>, Brice Goglin <brice@myri.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <greg@kroah.com>
Subject: Re: [RFC] PCI extended conf space when MMCONFIG disabled  because of e820
Date: Thu, 15 Jun 2006 06:18:52 -0700	[thread overview]
Message-ID: <44915E3C.5000608@linux.intel.com> (raw)
In-Reply-To: <200606150443_MC3-1-C283-D4F7@compuserve.com>

Chuck Ebbert wrote:
> In-Reply-To: <p73ac8fqjix.fsf@verdi.suse.de>
> 
> On 15 Jun 2006 03:45:10 +0200, Andi Kleen wrote:
> 
>> Anyways I would say that if the BIOS can't get MCFG right then 
>> it's likely not been validated on that board and shouldn't be used.
> 
> According to Petr Vandrovec:
> 
>  ... "What is important (and checked) is address of MMCONFIG reported by MCFG
>  table...  Unfortunately code does not bother with printing that address :-(
>  
>  "Another problem is that code has hardcoded that MMCONFIG area is 256MB large. 
>  Unfortunately for the code PCI specification allows any power of two between 2MB 
>  and 256MB if vendor knows that such amount of busses (from 2 to 128) will be 
>  sufficient for system.  With notebook it is quite possible that not full 8 bits 
>  are implemented for MMCONFIG bus number."
> 
> 
> So here is a patch.  Unfortunately my system still fails the test because
> it doesn't reserve any part of the MMCONFIG area, but this may fix others.
> 
> Booted on x86_64, only compiled on i386.  x86_64 still remaps the max area
> (256MB) even though only 2MB is checked... but 2.6.16 had no check at all
> so it is still better.
> 
> 
> PCI: reduce size of x86 MMCONFIG reserved area check
> 
> 1.  Print the address of the MMCONFIG area when the test for that area
>     being reserved fails.
> 
> 2.  Only check if the first 2MB is reserved, as that is the minimum.
> 
> Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>

Acked-by: Arjan van de Ven <arjan@linux.intel.com>


  reply	other threads:[~2006-06-15 13:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  8:41 [RFC] PCI extended conf space when MMCONFIG disabled because of e820 Chuck Ebbert
2006-06-15 13:18 ` Arjan van de Ven [this message]
2006-06-15 14:32   ` Barry Scott
  -- strict thread matches above, loose matches on Subject: below --
2006-06-14 21:07 Brice Goglin
2006-06-14 21:09 ` Arjan van de Ven
2006-06-15  1:45   ` Andi Kleen
2006-06-15  1:57   ` Brice Goglin
2006-06-15  6:47     ` Arjan van de Ven
2006-06-21 22:19       ` Rajesh Shah
2006-06-21 22:32         ` Andi Kleen
2006-06-22  0:15           ` Rajesh Shah
2006-06-22  9:27             ` Arjan van de Ven
2006-06-23  7:41               ` Rajesh Shah

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=44915E3C.5000608@linux.intel.com \
    --to=arjan@linux.intel.com \
    --cc=76306.1226@compuserve.com \
    --cc=ak@suse.de \
    --cc=brice@myri.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.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