linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.68-mm4 && kexec
Date: 04 May 2003 21:46:51 -0600	[thread overview]
Message-ID: <m1of2iawd0.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20030502020149.1ec3e54f.akpm@digeo.com>

Andrew Morton <akpm@digeo.com> writes:

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.68/2.5.68-mm4/
> 
> 
> . Much reworking of the disk IO scheduler patches due to the updated
>   dynamic-disk-request-allocation patch.  No real functional changes here.
> 
> . Included the `kexec' patch - load Linux from Linux.  Various people want
>   this for various reasons.  I like the idea of going from a login prompt to
>   "Calibrating delay loop" in 0.5 seconds.
> 
>   I tried it on four machines and it worked with small glitches on three of
>   them, and wedged up the fourth.  So if it is to proceed this code needs
>   help with testing and careful bug reporting please.

The current state of the code is that APM is not expected to work.  The
user space tool needs a fix to pass the address of the APM entry points
to the new kernel.

But beyond that everything should work baring drivers which have
problems shutting themselves down and restarting.

Eric

      parent reply	other threads:[~2003-05-05  3:37 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  9:01 2.5.68-mm4 Andrew Morton
2003-05-02 13:18 ` 2.5.68-mm4 William Lee Irwin III
2003-05-02 16:47   ` 2.5.68-mm4 Dave Hansen
2003-05-02 14:45 ` 2.5.68-mm4 Steven Cole
2003-05-02 15:00   ` 2.5.68-mm4 Steven Cole
2003-05-02 15:35 ` 2.5.68-mm4 Anton Blanchard
2003-05-03 14:12   ` 2.5.68-mm4 Eric W. Biederman
2003-05-02 16:54 ` 2.5.68-mm4 Martin J. Bligh
2003-05-02 20:04 ` 2.5.68-mm4 Steven Cole
2003-05-02 20:34   ` 2.5.68-mm4 Andrew Morton
2003-05-02 20:49     ` 2.5.68-mm4 Steven Cole
2003-05-02 21:01       ` 2.5.68-mm4 Steven Cole
2003-05-02 21:05       ` 2.5.68-mm4 Andrew Morton
2003-05-02 21:20         ` 2.5.68-mm4 Steven Cole
2003-05-02 21:49           ` 2.5.68-mm4 Andy Pfiffer
2003-05-02 22:00             ` 2.5.68-mm4 Steven Cole
2003-05-02 23:22           ` 2.5.68-mm4 Matt Bernstein
2003-05-02 23:41             ` 2.5.68-mm4 Andrew Morton
2003-05-03  2:53               ` 2.5.68-mm4 Andi Kleen
2003-05-03  7:08                 ` 2.5.68-mm4 Matt Bernstein
     [not found]                   ` <Pine.LNX.4.55.0305061511020.3237@r2-pc.dcs.qmul.ac.uk>
2003-05-06 14:35                     ` 2.5.68-mm4 Andi Kleen
2003-05-06 15:50                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 10:27                       ` 2.5.68-mm4 Matt Bernstein
2003-05-07 12:35                         ` 2.5.68-mm4 Andi Kleen
2003-05-07 15:45                           ` 2.5.68-mm4 Matt Bernstein
2003-05-03  3:14               ` 2.5.68-mm4 Andi Kleen
2003-05-03 13:51               ` 2.5.68-mm4 Diego Calleja García
2003-05-03  1:14     ` 2.5.68-mm4 Herbert Xu
2003-05-05  3:46 ` Eric W. Biederman [this message]

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=m1of2iawd0.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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).