[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131121190710.GD17070@kroah.com>
Date: Thu, 21 Nov 2013 11:07:10 -0800
From: Greg KH <greg@...ah.com>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: linux-kernel@...r.kernel.org, kexec@...ts.infradead.org,
ebiederm@...ssion.com, hpa@...or.com, mjg59@...f.ucam.org
Subject: Re: [PATCH 5/6] kexec-bzImage: Support for loading bzImage using
64bit entry
On Wed, Nov 20, 2013 at 12:50:50PM -0500, Vivek Goyal wrote:
> 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
> yet.
>
> Signed-off-by: Vivek Goyal <vgoyal@...hat.com>
> ---
> arch/x86/include/asm/kexec-bzimage.h | 12 +
> arch/x86/include/asm/kexec.h | 26 +++
> arch/x86/kernel/Makefile | 2 +
> arch/x86/kernel/kexec-bzimage.c | 375 ++++++++++++++++++++++++++++++++++
> arch/x86/kernel/machine_kexec_64.c | 4 +-
> arch/x86/kernel/purgatory_entry_64.S | 119 +++++++++++
> 6 files changed, 537 insertions(+), 1 deletions(-)
> create mode 100644 arch/x86/include/asm/kexec-bzimage.h
> create mode 100644 arch/x86/kernel/kexec-bzimage.c
> create mode 100644 arch/x86/kernel/purgatory_entry_64.S
Wow, that's surprisingly small, nice job.
What do you mean by the "real mode entry"? Do we need to care about
that because we aren't falling back to real mode when executing this,
are we? Or does that just happen for 32bit kernels?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists