mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: ebiederm@xmission.com, rddunlap@osdl.org, davidm@hpl.hp.com,
	fastboot@lists.osdl.org, linux-kernel@vger.kernel.org,
	drepper@redhat.com
Subject: Re: [Fastboot] Re: [announce] kexec for linux 2.6.6
Date: Thu, 13 May 2004 01:04:27 -0700	[thread overview]
Message-ID: <20040513010427.0e4fe22c.akpm@osdl.org> (raw)
In-Reply-To: <20040513084931.A6858@infradead.org>

Christoph Hellwig <hch@infradead.org> wrote:
>
> On Thu, May 13, 2004 at 12:37:27AM -0700, Andrew Morton wrote:
> > The (old) kexec patch I have here implements the API which is described at
> > http://lwn.net/Articles/15468/.  I doubt if it changed?
> 
> That API looks sane to me.

yup.  Here's the syscall itself, btw:

+/*
+ * Exec Kernel system call: for obvious reasons only root may call it.
+ * 
+ * This call breaks up into three pieces.  
+ * - A generic part which loads the new kernel from the current
+ *   address space, and very carefully places the data in the
+ *   allocated pages.
+ *
+ * - A generic part that interacts with the kernel and tells all of
+ *   the devices to shut down.  Preventing on-going dmas, and placing
+ *   the devices in a consistent state so a later kernel can
+ *   reinitialize them.
+ *
+ * - A machine specific part that includes the syscall number
+ *   and the copies the image to it's final destination.  And
+ *   jumps into the image at entry.
+ *
+ * kexec does not sync, or unmount filesystems so if you need
+ * that to happen you need to do that yourself.
+ */
+struct kimage *kexec_image = 0;
+
+asmlinkage long sys_kexec_load(unsigned long entry, unsigned long nr_segments, 
+	struct kexec_segment *segments, unsigned long flags)
+{

+struct kexec_segment {
+	void *buf;
+	size_t bufsz;
+	void *mem;
+	size_t memsz;
+};


  reply	other threads:[~2004-05-13  8:06 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-12  4:26 Randy.Dunlap
2004-05-12  5:00 ` Ulrich Drepper
2004-05-12  6:18   ` [Fastboot] " Eric W. Biederman
2004-05-12 15:33     ` Ulrich Drepper
2004-05-12 15:54       ` Eric W. Biederman
2004-05-12 16:31         ` Ulrich Drepper
2004-05-12 16:57           ` Eric W. Biederman
2004-05-12 21:32             ` Randy.Dunlap
2004-05-12 22:08               ` David Mosberger
2004-05-12 22:28                 ` Andrew Morton
2004-05-12 22:33                   ` David Mosberger
2004-05-12 23:16                     ` Andrew Morton
2004-05-12 23:27                       ` David Mosberger
2004-05-13  4:30                       ` Christoph Hellwig
2004-05-13  5:05                         ` Willy Tarreau
2004-05-13  5:21                           ` William Lee Irwin III
2004-05-13  5:48                           ` Christoph Hellwig
2004-05-13  6:06                         ` Eric W. Biederman
2004-05-13  6:20                           ` Andrew Morton
2004-05-13  6:39                             ` Eric W. Biederman
2004-05-13  7:33                           ` Christoph Hellwig
2004-05-13  7:37                             ` Andrew Morton
2004-05-13  7:49                               ` Christoph Hellwig
2004-05-13  8:04                                 ` Andrew Morton [this message]
2004-05-13 13:52                                   ` Eric W. Biederman
2004-05-13 15:02                                 ` Randy.Dunlap
2004-05-14  5:21               ` Eric W. Biederman
2004-05-14 18:14                 ` Adam Litke
2004-05-15  2:25                   ` Eric W. Biederman
2004-05-17  0:49                     ` H. Peter Anvin
2004-05-12  5:05 ` [Fastboot] " 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=20040513010427.0e4fe22c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davidm@hpl.hp.com \
    --cc=drepper@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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

all inboxes | Powered by JetHome®