From: Avery Pennarun <apenwarr@xxxxxxxxx> Date: Tue, 13 Mar 2012 03:14:21 -0400 > On Tue, Mar 13, 2012 at 2:50 AM, David Miller <davem@xxxxxxxxxxxxx> wrote: >> The idea is that you call prom_retain() before you take a look at what >> physical memory is available in the kernel, and the firmware takes >> this physical chunk out of those available memory lists upon >> prom_retain() success. > > This sounds like exactly the API I would have wanted, however: > > 1) It's only available in arch/sparc so I can't test my patch if I try > to use it; > 2) There's nobody that calls it so it might not work; > 3) I don't understand the API so I'm not really confident that > reserving memory this way will actually prevent it from being seen by > the kernel. > > In short, I think I would screw it up. I'm only saying that you should design your stuff such that an architecture with such features could easily hook into it using this kind facility. -- 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>