From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Jeremy Fitzhardinge <jeremy@xensource.com>
Cc: konradr@us.ibm.com, Jeremy Fitzhardinge <jeremy@goop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arjan@linux.intel.com, linux-acpi@vger.kernel.org
Subject: Re: ThinkPad X60: PCI: BIOS Bug: MCFG area is not E820-reserved (MCFG is in ACPI NVS)
Date: Wed, 31 May 2006 01:06:26 +0200 [thread overview]
Message-ID: <447CCFF2.30207@vc.cvut.cz> (raw)
In-Reply-To: <1149025621.25497.9.camel@jeremy.eng.hq.xensource.com>
Jeremy Fitzhardinge wrote:
> On Tue, 2006-05-30 at 16:41 -0400, konradr@us.ibm.com wrote:
>
>>On Tue, May 30, 2006 at 12:38:01PM -0700, Jeremy Fitzhardinge wrote:
>>
>>>[snip]
>>>
>>>So the MCFG entry is in the ACPI NVS region of the E820 table. Is this
>>>bad?
>>
>>Not at all. The ACPI v3.0 specs mentions that:
>>
>>"ACPI NVS Memory. This range of addresses is in use or reserve by
>>the system and must not be used by the operating system. This
>>range is required to be saved and restored across an NVS sleep."
>
>
> I actually misread the tables. It appears that MCFG (at 0x7f6e2e36) is
> in ACPI Data (7f6d0000 - 7f6e3000). include/asm-i386/e820.h says that
> memory marked as "E820_ACPI" can be reused as normal memory once the
> ACPI tables have been read.
>
> Doesn't this mean that the MCFG memory could end up being used as
> general system memory? That seems bad if MCFG memory is some kind of
> MMIO space. Or is the comment simply wrong?
Address where MCFG table lives is not important. 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.
Petr
next prev parent reply other threads:[~2006-05-30 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <447C9F19.5000105@goop.org>
[not found] ` <20060530204112.GA22031@andromeda.dapyr.net>
2006-05-30 21:47 ` ThinkPad X60: PCI: BIOS Bug: MCFG area is not E820-reserved (MCFG is in ACPI NVS) Jeremy Fitzhardinge
2006-05-30 23:06 ` Petr Vandrovec [this message]
2006-05-30 23:48 ` Greg KH
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=447CCFF2.30207@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=arjan@linux.intel.com \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=konradr@us.ibm.com \
--cc=linux-acpi@vger.kernel.org \
--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