public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andy Pfiffer <andyp@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	fastboot@osdl.org
Subject: Re: kexec for 2.5.46
Date: 06 Nov 2002 22:14:43 -0700	[thread overview]
Message-ID: <m1fzuedkqk.fsf@frodo.biederman.org> (raw)
In-Reply-To: <1036631471.10457.233.camel@andyp>

Andy Pfiffer <andyp@osdl.org> writes:

> On Tue, 2002-11-05 at 22:38, Eric W. Biederman wrote:
> > Linus please apply,
> 
> 
> FYI: patch applied cleanly for me.
> 
> After fudging kexec-tools-1.4 to correct for the new syscall number:
>     <hang>
> 
> It does not make it to the "Interrupts enabled." print, so it is
> probably going wacko at the "sti."

Thanks for the report.  Linus has asked for some changes, but has
ok'd. the basic idea the thread topic on linux-kernel was: 
"Re: [lkcd-devel] Re: What's left over." 
I am going to focus on getting those changes made, and then I
concentrate on why things fail in strange ways for various people. 

The primary change is that the mcore people need a 2 stage kexec.  1
load the kernel.  2 later actually start it.  This allows the second
kernel to be started when the first kernel panics.  Allowing for
nice crash dumps and perhaps some other interesting debugging
techniques.

Talk to you later...

Eric

  reply	other threads:[~2002-11-07  5:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  6:38 kexec for 2.5.46 Eric W. Biederman
2002-11-07  1:11 ` Andy Pfiffer
2002-11-07  5:14   ` Eric W. Biederman [this message]
2002-11-11  3:59   ` Eric W. Biederman

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=m1fzuedkqk.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=andyp@osdl.org \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.kernel.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