> Hi,
> There have been several machines that don't have a working MMCONFIG,
> often because of a buggy MCFG table in the ACPI bios. This patch adds a
> simple sanity check that detects a whole bunch of these cases, and when
> it detects it, linux now boots rather than crash-and-burns.
> [snip]
Arjan,
I am not sure if your analysis and your solution to the problem is correct.
It was my understanding that any memory NOT defined in the E820 tables
is NOT considered system memory. Therefore memory addresses defined in the
ACPI MCFG table do not have to show up in the E820 table.
Also the ACPI spec v3.0 (pg 405 of PDF, section 14.2, titled:
"E820 Assumptions and Limitations") agrees with this:
"The BIOS does not return a range description for the memory mapping
of PCI devices, ISA Option ROMs, and the ISA PNP cards because the OS
has mechanisms available to detect them."
(The ACPI v2.0c spec has this in section 15.2).
Obviously specifications are sometimes outdated, or assumptions are made in
some specifications which are not in other specification, so I was wondering
if you could tell me which specification defines that the memory addresses
in ACPI MCFG table have to be reserved in the E820 tables?
If this is not a specification issue, I was wondering if perhaps for the
machines you refer to, their BIOS bug is that the E820 have memory ranges
which also encompass what MMCONF points to?
Thanks!
Konrad Rzeszutek
IBM, (617)-693-1718
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
