All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, Andi Kleen <ak@suse.de>
Subject: Re: PCI Express MMCONFIG and BIOS Bug messages..
Date: Thu, 19 Apr 2007 12:05:44 -0400	[thread overview]
Message-ID: <46279358.1010002@redhat.com> (raw)
In-Reply-To: <4626C514.5010605@shaw.ca>

Robert Hancock wrote:
> I've seen a lot of systems (including brand new Xeon-based servers from
> IBM and HP) that output messages on boot like:
> 
> PCI: BIOS Bug: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> 
> 
> So Microsoft is explicitly telling the BIOS developers that there is no
> need to reserve the MMCONFIG space in the E820 table because Windows
> doesn't care. On that basis it doesn't seem like a valid check to
> require it to be so reserved, then.
> 
> Really, I think we should be basing this check on whether the
> corresponding memory range is reserved in the ACPI resources, like
> Windows expects. This does require putting more fingers into ACPI from
> this early boot stage, though..
> 

Intel had posted patches to do exactly that, but they were rejected.
I don't remember why now...

  reply	other threads:[~2007-04-19 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-19  1:25 PCI Express MMCONFIG and BIOS Bug messages Robert Hancock
2007-04-19 16:05 ` Chuck Ebbert [this message]
2007-04-29  1:22   ` Robert Hancock
2007-04-29 10:12     ` Andi Kleen
2007-04-29 18:20       ` Robert Hancock
2007-04-29 18:27         ` Jesse Barnes
2007-04-29 18:39           ` Robert Hancock

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=46279358.1010002@redhat.com \
    --to=cebbert@redhat.com \
    --cc=ak@suse.de \
    --cc=hancockr@shaw.ca \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.