On Thu, Dec 21, 2006 at 05:36:25PM +0900, Magnus Damm wrote: > > I would focus on getting kexec to work properly first if I were you. > And when that is in place I would spend time on fixing up kdump. The > kdump chain is pretty complex, and the kexec user space code is pretty > hairy. So after fixing up kexec you need to make sure the kdump chain > works. This is very similar to the work that we have been doing with > out Xen port. > > Like I said - the kdump chain is pretty complex, but I've found myself > spending way too much time on the kexec user space tool itself. Simon, > I and other people on the list have lately been working on cleaning up > the code base - so again - I strongly recommend you to build on that > code.
Hi Larry, After porting and reporting kexec to xen several times on several architectures, my advice is to get UP (maxcpus=1 is fine) kexec working first. Once thats working build up SMP and kdump support like Magnus suggests. -- Horms H: http://www.vergenet.net/~horms/ W: http://www.valinux.co.jp/en/ _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
