linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortel.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org
Subject: status of kexec for ppc on 2.6.10, any gotchas?
Date: Thu, 20 Oct 2005 23:03:52 -0600	[thread overview]
Message-ID: <435876B8.9000706@nortel.com> (raw)


I've been asked to look at kexec for ppc on 2.6.10.  The syscall appears 
to be present, but there seem to be additional patches for 2.6.10-mm at:

http://www.xmission.com/~ebiederm/files/kexec/

Are these patches needed?

I haven't been able to find any current official documentation, although 
I found some old stuff from 2.5 and a writeup at:
 
http://www-128.ibm.com/developerworks/linux/library/l-kexec.html?ca=dgr-lnxw04RebootFast

Is there any official HOWTO on this?  Any issues I should look at in 
particular?

Thanks for any pointers,

Chris

             reply	other threads:[~2005-10-21  5:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21  5:03 Christopher Friesen [this message]
2005-10-21 11:02 ` status of kexec for ppc on 2.6.10, any gotchas? R Sharada

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=435876B8.9000706@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).