On Sat, Nov 24, 2012 at 3:50 PM, Eric W. Biederman <ebied...@xmission.com> wrote: > > I believe all added variables between the last version of the boot > protocol /sbin/kexec knows about and the current time were added in the > initialized data section. Certainly we can check and that will tell us > how likely changes in arch/x86/boot/ have been regressions in the 32bit > entry point support. > > As for solving this there is a simple solution. Add a second jump > right after the first jump. The variables after the second jump can > all be zero initialized.
could use .org to force start_of_setup start from 0x1000 but how about area before setup_header ? how it is full of EFI_STUB suff there. Yinghai -- 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/
