On Mon, Sep 30, 2013 at 11:06:46PM +0200, Borislav Petkov wrote: > On Mon, Sep 30, 2013 at 04:46:42PM -0400, Vivek Goyal wrote: > > On Mon, Sep 30, 2013 at 10:41:54PM +0200, Borislav Petkov wrote: > > > > [..] > > > hpa, so, for the struct efi_mapping thing to work, I will have to grep > > > dmesg of the first kernel to get an output like the one below, filter > > > the runtime regions so that I can build the struct efi_mapping array of > > > mem regions which I pass on to the second, kexec kernel with setup_data. > > > > Any data you need to pass to second kernel will have to be exported to > > user space either using /sys or /proc so that kexec-tools can parse it. > > And I cannot parse dmesg? Because I have all the info there already.
dmesg can 't relied on. It is just a kernel buffer which root can clear. (dmesg --clear). So required info has to be exported to user space in a suitable form. Thanks Vivek -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
