Re: [Fastboot] [announce] kexec for linux 2.6.6

[Eric W. Biederman]

"Randy.Dunlap" <rddunlap@xxxxxxxx> 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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/