kexec-bzImage64: support for loading bzImage using 64bit entry
This is loader specific code which can load bzImage and set it up for 64bit entry. This does not take care of 32bit entry or real mode entry. 32bit mode entry can be implemented if somebody needs it. Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Cc: Borislav Petkov <bp@suse.de> Cc: Michael Kerrisk <mtk.manpages@gmail.com> Cc: Yinghai Lu <yinghai@kernel.org> Cc: Eric Biederman <ebiederm@xmission.com> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Matthew Garrett <mjg59@srcf.ucam.org> Cc: Greg Kroah-Hartman <greg@kroah.com> Cc: Dave Young <dyoung@redhat.com> Cc: WANG Chao <chaowang@redhat.com> Cc: Baoquan He <bhe@redhat.com> Cc: Andy Lutomirski <luto@amacapital.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:

committed by
Linus Torvalds

parent
12db5562e0
commit
27f48d3e63
@@ -460,6 +460,14 @@ static void kimage_file_post_load_cleanup(struct kimage *image)
|
||||
|
||||
/* See if architecture has anything to cleanup post load */
|
||||
arch_kimage_file_post_load_cleanup(image);
|
||||
|
||||
/*
|
||||
* Above call should have called into bootloader to free up
|
||||
* any data stored in kimage->image_loader_data. It should
|
||||
* be ok now to free it up.
|
||||
*/
|
||||
kfree(image->image_loader_data);
|
||||
image->image_loader_data = NULL;
|
||||
}
|
||||
|
||||
/*
|
||||
@@ -576,7 +584,6 @@ out_free_control_pages:
|
||||
kimage_free_page_list(&image->control_pages);
|
||||
out_free_post_load_bufs:
|
||||
kimage_file_post_load_cleanup(image);
|
||||
kfree(image->image_loader_data);
|
||||
out_free_image:
|
||||
kfree(image);
|
||||
return ret;
|
||||
@@ -900,8 +907,6 @@ static void kimage_free(struct kimage *image)
|
||||
/* Free the kexec control pages... */
|
||||
kimage_free_page_list(&image->control_pages);
|
||||
|
||||
kfree(image->image_loader_data);
|
||||
|
||||
/*
|
||||
* Free up any temporary buffers allocated. This might hit if
|
||||
* error occurred much later after buffer allocation.
|
||||
|
Reference in New Issue
Block a user