On Mon, 2007-12-10 at 17:31 -0500, Vivek Goyal wrote:
> [..]
> >
> > -#define KEXEC_ON_CRASH 0x00000001
> > -#define KEXEC_ARCH_MASK 0xffff0000
> > +#define KEXEC_ON_CRASH 0x00000001
> > +#define KEXEC_PRESERVE_CPU 0x00000002
> > +#define KEXEC_PRESERVE_CPU_EXT 0x00000004
> > +#define KEXEC_SINGLE_CPU 0x00000008
> > +#define KEXEC_PRESERVE_DEVICE 0x00000010
> > +#define KEXEC_PRESERVE_CONSOLE 0x00000020
>
> Hi,
>
> Why do we need so many different flags for preserving different types
> of state (CPU, CPU_EXT, Device, console) ? To keep things simple,
> can't we can create just one flag KEXEC_PRESERVE_CONTEXT, which will
> indicate any special action required for preserving the previous kernel's
> context so that one can swith back to old kernel?
Yes. There are too many flags, especially when we have no users of these
flags now. It is better to use one flag such as KEXEC_PRESERVE_CONTEXT
now, and create the others required flags when really needed.
Best Regards,
Huang Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
