From: ebiederm@xmission.com (Eric W. Biederman)
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: fastboot@lists.osdl.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] [announce] kexec for linux 2.6.6
Date: 11 May 2004 23:05:13 -0600 [thread overview]
Message-ID: <m1ekpq5j7a.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20040511212625.28ac33ef.rddunlap@osdl.org>
"Randy.Dunlap" <rddunlap@osdl.org> writes:
> kexec for Linux 2.6.6 is now available at:
> http://developer.osdl.org/rddunlap/kexec/2.6.6/
>
>
> kexec userspace tools are at:
> http://developer.osdl.org/rddunlap/kexec/kexec-tools/
>
>
> For 2.6.6, the kexec_load syscall number had to move due to
> some new syscall additions in 2.6.6. However, I didn't
> update the kexec userspace program for that 1-line change.
> The change is in kexec-syscall.c, line 46:
>
> change
> #define __NR_kexec_load 274
> to
> #define __NR_kexec_load 283
>
> (for i386).
>
> There is one outstanding patch from Albert Herranz
> that I will review and possibly use/merge soon.
> His email is here:
> http://lists.osdl.org/pipermail/fastboot/2004-May/000290.html
>
>
> And if anyone has suggestions for handling a variable/moving
> syscall number (target), I'm interested in hearing them.
The easiest would be to update the ./configure script, and
have the syscall number as a parameter. Quite possibly it
could just point to an appropriate file that would grep for
__NR_kexec_load. This does not prevent the recompile problem
but it does help a little.
On the issue of needing $BIGNUM testers, I see a small challenge.
kexec is near useless on an unstable kernel. So it really needs
to get into a stable series or people will be fighting kernel
bugs so much that they won't be able to see kexec specific issues.
Possibly the sanest route is 2.7.early and then 2.6 at about
the same time. At any point that kexec makes it into a mainline
kernel though the syscall number will be frozen and things will
get easier.
Eric
prev parent reply other threads:[~2004-05-12 5: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
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 ` 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=m1ekpq5j7a.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.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®