2013/01/19 3:29, Luck, Tony wrote:
kernel absolutely should not care much about SMBIOS(DMI info),
AFAIK, every BIOS vendor did not fill accurate info in SMBIOS,
mostly only on demand when OEMs required SMBIOS to report some
specific info.
furthermore, SMBIOS is so old and benifit nobody(in my personal
opinion), so maybe let's forget it.
The "not having right information" flaw could be fixed by OEMs selling
systems on which it is important for system functionality that it be right.
They could use monetary incentives, contractual obligations, or sharp
pointy sticks to make their BIOS vendor get the table right.
BUT there is a bigger flaw - SMBIOS is a static table with no way to
update it in response to hotplug events. So it could in theory have the
right information at boot time ... there is no possible way for it to be
right as soon as somebody adds, removes or replaces hardware.
Using DMI information depends on firmware strongly. So even if we
implement boot option which uses DMI information for specifying memory
range as Movable zone, we cannot use it on our box. Other users may
hit same problem.
So we want to keep a current boot option which specifies memory range
since user can know memory address on every box.
Thanks,
Yasuaki Ishimatsu
-Tony
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>