public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Larry McVoy <lm@bitmover.com>
Cc: RaXlNXXez de Arenas Coronado <dervishd@jazzfree.com>,
	linux-kernel@vger.kernel.org
Subject: Re: LOBOS (kexec)
Date: 19 Nov 2001 20:11:28 -0700	[thread overview]
Message-ID: <m1elmu6srj.fsf_-_@frodo.biederman.org> (raw)
In-Reply-To: <E165yPH-000040-00@DervishD> <20011119181731.D23210@work.bitmover.com>
In-Reply-To: <20011119181731.D23210@work.bitmover.com>

Larry McVoy <lm@bitmover.com> writes:

> I've been wanting Linux which can boot Linux for a long time.
> See http://www.bitmover.com/ml for some slides on why, for those of you
> who are guess, yes it is the same OS cluster idea for SMP scaling I've
> been pushing on for 7 years.  It's finally getting some attention as
> well, the IBM guys are looking at it, a FreeBSD guy is looking at it,
> and the UML guy thinks he can do a UML implementation in such a way 
> that putting it on real hardware would be a "simple" port.

I am maintaining a version of this functionality against 2.4.x
called kexec.  And I plan to work on integration into linux with 2.5.x.
After the details are worked out I will look at a backport to 2.4.x

The hard part is not linux booting linux but the passing of the
firmware/BIOS tables from one kernel to the next.  Especially those
that can only be obtained by a 16bit query.  It is my assumption that
after the OS runs you cannot return to the firmware, it's state is
hopelessly mangled.  That may not be totally true but it is fairly
close to the truth. 

I am doing this a part of the linuxBIOS effort and as such it is just
maturing enough that I can really start concentrating on this aspect
of the problem.  I do not want an interface that is mushy.  I want an
interface that is extensible.  But is pretty much frozen for all time
like the ELF file format.

My patches show up from time to time at:
ftp://download.linuxnetworx.com/pub/src/kernel-patches/

Hopefully soon I will get my port to 2.4.14 put up there soon.  
I have been maintaining and this since 2.4.0-pre9 or so.  And I have
been using this actively.  And I have an alpha port.  I would port to
other architectures but I don't have the machines available.

Eric


  parent reply	other threads:[~2001-11-20  3:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20  0:04 LOBOS RaúlNúñez de Arenas Coronado
2001-11-20  2:17 ` LOBOS Larry McVoy
2001-11-20  2:03   ` LOBOS Tim Hockin
2001-11-20  2:42     ` LOBOS Erik Andersen
2001-11-20  3:11   ` Eric W. Biederman [this message]
2001-11-20  5:41     ` LOBOS (kexec) Tim Hockin
2001-11-20  6:52       ` Eric W. Biederman
2001-11-20 23:56     ` Werner Almesberger
2001-11-21  2:53       ` Eric W. Biederman
2001-11-21 17:11         ` Randy.Dunlap
2001-11-22  6:37           ` Eric W. Biederman
2001-11-20  2:19 ` LOBOS victor
  -- strict thread matches above, loose matches on Subject: below --
2001-11-20 12:22 LOBOS (kexec) RaúlNúñez de Arenas Coronado
2001-11-20 13:40 ` 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=m1elmu6srj.fsf_-_@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=dervishd@jazzfree.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox