On Jul 18, 2010, at 7:09 PM, Benjamin Herrenschmidt wrote: > On Thu, 2010-07-15 at 10:22 -0600, Grant Likely wrote: >> What is your starting point? Where does the device tree (and >> memreserve list) come from >> that you're passing to kexec? My first impression is that if you have >> to scrub the memreserve list, then the source being used to >> obtain the memreserves is either faulty or unsuitable to the task. > > The kernel should ultimately pass the thing to userspace I reckon, with > an appropriate hook for platform code to insert/recover reserved > regions. >
Or possibly in the device tree itself? As I mentioned in my previous email - my particular case can already be handled by the information passed in the device tree (as I recently discovered), is this something we would want to make generic for the device tree or add platform code to expose these memreserve regions? -Matthew _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
