On Fri, 11 May 2012 13:46:04 +0800 Lai Jiangshan <laijs@xxxxxxxxxxxxxx> wrote: > Current ZONE_MOVABLE (kernelcore=) setting policy with boot option doesn't meet > our requirement. We need something like kernelcore_max_addr= boot option > to limit the kernelcore upper address. Why do you need this? Please fully describe the requirement/use case. > The memory with higher address will be migratable(movable) and they > are easier to be offline(always ready to be offline when the system don't require > so much memory). > > All kernelcore_max_addr=, kernelcore= and movablecore= can be safely specified > at the same time(or any 2 of them). -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>