On Sat, Jul 16, 2011 at 09:16:06AM -0700, Eric W. Biederman wrote: [..] > Am I wrong in thinking that the core motivation behind this patch is > that our EFI support sucks and thus kdump on EFI does not work on some > platforms? One of the arguments seems is that kdump might not work 100% of the time and saving kernel messages atleast gets some information out reliably. I think being able to save dmesg to NVRAM, in general sounds good to me (if done in a relatively clean manner). Especially if we can get rid of code taking locks and code path executed after crash is not tool long and relatively easy to audit. Thanks Vivek
