From: Randy Dunlap <randy.dunlap@oracle.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Bernhard Walle <bwalle@suse.de>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [PATCH] Fix kexec x86_64 load failed bug
Date: Tue, 25 Nov 2008 19:25:30 -0800 [thread overview]
Message-ID: <492CC1AA.3010408@oracle.com> (raw)
In-Reply-To: <1227662409.2442.11.camel@yhuang-dev.sh.intel.com>
Huang Ying wrote:
> Fix a bug of kexec load on x86_64. Kexec fails to do load on x86_64, with
> error message:
>
> Symbol: cmdline_end not found cannot set
>
> Because kexec/arch/i386/kexec-bzImage.c accesses cmdline_end symbol in
> i386 purgatory, but there is no cmdline_end in x86_64 purgatory, and
> kexec-bzImage.c is used by x86_64 too.
>
> cmdline_end is added into x86_64 purgatory to solve the bug, because kexec
> jump support for x86_64 is planned.
>
> Reported-by: Bernhard Walle <bwalle@suse.de>
> Signed-off-by: Huang Ying <ying.huang@intel.com>
>
> diff --git a/purgatory/arch/x86_64/purgatory-x86_64.c b/purgatory/arch/x86_64/purgatory-x86_64.c
> index 374b554..67a37f9 100644
> --- a/purgatory/arch/x86_64/purgatory-x86_64.c
> +++ b/purgatory/arch/x86_64/purgatory-x86_64.c
> @@ -5,6 +5,7 @@
> uint8_t reset_vga = 0;
> uint8_t legacy_pic = 0;
> uint8_t panic_kernel = 0;
> +char *cmdline_end = 0;
>
> void setup_arch(void)
> {
This isn't kernel code? Where is /purgatory/ ?
Anyway, for kernel code, that should be:
char *cmdline_end = NULL;
--
~Randy
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-11-26 3:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 12:47 kexec does not load Bernhard Walle
2008-11-26 1:20 ` [PATCH] Fix kexec x86_64 load failed bug Huang Ying
2008-11-26 3:25 ` Randy Dunlap [this message]
2008-11-26 4:25 ` Huang Ying
2008-11-26 6:16 ` Simon Horman
2008-11-26 6:47 ` Huang Ying
2008-11-26 7:48 ` Simon Horman
2008-11-26 9:07 ` Bernhard Walle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=492CC1AA.3010408@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=bwalle@suse.de \
--cc=kexec@lists.infradead.org \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.