Re: [PATCH v5 0/5] Add movablecore_map boot option

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Jan 19, 2013 at 09:06:14AM +0800, Jiang Liu wrote:
> Date: Sat, 19 Jan 2013 09:06:14 +0800
> From: Jiang Liu <jiang.liu@xxxxxxxxxx>
> To: "Luck, Tony" <tony.luck@xxxxxxxxx>
> CC: li guang <lig.fnst@xxxxxxxxxxxxxx>, Tang Chen
>  <tangchen@xxxxxxxxxxxxxx>, Yasuaki Ishimatsu
>  <isimatu.yasuaki@xxxxxxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, KOSAKI
>  Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>, "akpm@xxxxxxxxxxxxxxxxxxxx"
>  <akpm@xxxxxxxxxxxxxxxxxxxx>, "wujianguo@xxxxxxxxxx"
>  <wujianguo@xxxxxxxxxx>, "wency@xxxxxxxxxxxxxx" <wency@xxxxxxxxxxxxxx>,
>  "laijs@xxxxxxxxxxxxxx" <laijs@xxxxxxxxxxxxxx>, "linfeng@xxxxxxxxxxxxxx"
>  <linfeng@xxxxxxxxxxxxxx>, "yinghai@xxxxxxxxxx" <yinghai@xxxxxxxxxx>,
>  "rob@xxxxxxxxxxx" <rob@xxxxxxxxxxx>, "minchan.kim@xxxxxxxxx"
>  <minchan.kim@xxxxxxxxx>, "mgorman@xxxxxxx" <mgorman@xxxxxxx>,
>  "rientjes@xxxxxxxxxx" <rientjes@xxxxxxxxxx>, "guz.fnst@xxxxxxxxxxxxxx"
>  <guz.fnst@xxxxxxxxxxxxxx>, "rusty@xxxxxxxxxxxxxxx"
>  <rusty@xxxxxxxxxxxxxxx>, "lliubbo@xxxxxxxxx" <lliubbo@xxxxxxxxx>,
>  "jaegeuk.hanse@xxxxxxxxx" <jaegeuk.hanse@xxxxxxxxx>,
>  "glommer@xxxxxxxxxxxxx" <glommer@xxxxxxxxxxxxx>,
>  "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>,
>  "linux-mm@xxxxxxxxx" <linux-mm@xxxxxxxxx>
> Subject: Re: [PATCH v5 0/5] Add movablecore_map boot option
> User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222
>  Thunderbird/9.0.1
> 
> On 2013-1-19 2: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.
> 
> SMBIOS plays an important role when we are trying to do hardware fault
> management, because OS needs information from SMBIOS to physically
> identify a component/FRU. I also remember there were efforts to extend
> SMBIOS specification to dynamically update the SMBIOS table when hotplug
> happens.

Really, how to do it? Can you describe it clearly. BTW, if my understanding
is right, new Platform Memory Topology Table (PMTT) in ACPI5 should be for
this purpose but it doesn't exist in the older system so I want to know if
there is a workaround for older platform.

> 
> Regards!
> Gerry
> 
> > 
> > -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>

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]