On Thu, Nov 18, 2010 at 12:48:50PM +0800, Shaohui Zheng wrote: > On Wed, Nov 17, 2010 at 01:18:50PM -0800, David Rientjes wrote: > > Then, export the amount of memory that is actually physically present in > > the e820 but was truncated by mem= and allow users to hot-add the memory > > via the probe interface. Add a writeable 'node' file to offlined memory > > section directories and allow it to be changed prior to online. > > for memory offlining, it is a known diffcult thing, and it is not supported > well in current kernel, so I do not suggest to provide the offline interface > in the emulator, it just take more pains. We can consider to add it when > the memory offlining works well. > This is all stuff that the memblock API can deal with, I'm not sure why there seems to be an insistence on wedging all manner of unrelated bits in to e820. Many platforms using memblock today already offline large amounts of contiguous physical memory for use in drivers, if you were to follow this scheme and simply layer a node creation shim on top of that you would end up with something that is almost entirely generic. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>