On Mon, 2007-12-10 at 19:25 -0700, Eric W. Biederman wrote:
> "Huang, Ying" <ying.huang@xxxxxxxxx> writes:
[...]
> > /*
> > * Do not allocate memory (or fail in any way) in machine_kexec().
> > * We are past the point of no return, committed to rebooting now.
> > */
> > -NORET_TYPE void machine_kexec(struct kimage *image)
> > +int machine_kexec_vcall(struct kimage *image, unsigned long *ret,
> > + unsigned int argc, va_list args)
> > {
>
> Why do we need var arg support?
> Can't we do that with a shim we load from user space?
If all parameters are provided in user space, the usage model may be as
follow:
- sys_kexec_load() /* with executable/data/parameters(A) loaded */
- sys_reboot(,,LINUX_REBOOT_CMD_KEXEC,) /* execute physical mode code with parameters(A)*/
- /* jump back */
- sys_kexec_load() /* with executable/data/parameters(B) loaded */
- sys_reboot(,,LINUX_REBOOT_CMD_KEXEC,) /* execute physical mode code with parameters(B)*/
- /* jump back */
That is, the kexec image should be re-loaded if the parameters are
different, and there can be no state reserved in kexec image. This is OK
for original kexec implementation, because there is no jumping back.
But, for kexec with jumping back, another usage model may be useful too.
- sys_kexec_load() /* with executable/data loaded */
- sys_reboot(,,LINUX_REBOOT_CMD_KEXEC,parameters(A)) /* execute physical mode code with parameters(A)*/
- sys_reboot(,,LINUX_REBOOT_CMD_KEXEC,parameters(B)) /* execute physical mode code with parameters(B)*/
This way the kexec image need not to be re-loaded, and the state of
kexec image can be reserved across several invoking.
Another usage model may be useful is invoking the kexec image (such as
firmware) from kernel space.
- kmalloc the needed memory and loaded the firmware image (if needed)
- sys_kexec_load() with a fake image (one segment with size 0), the
entry point of the fake image is the entry point of the firmware image.
- kexec_call(fake_image, ...) /* maybe change entry point if needed */
This way, some kernel code can invoke the firmware in physical mode just
like invoking an ordinary function.
[...]
> > - /* The segment registers are funny things, they have both a
> > - * visible and an invisible part. Whenever the visible part is
> > - * set to a specific selector, the invisible part is loaded
> > - * with from a table in memory. At no other time is the
> > - * descriptor table in memory accessed.
> > - *
> > - * I take advantage of this here by force loading the
> > - * segments, before I zap the gdt with an invalid value.
> > - */
> > - load_segments();
> > - /* The gdt & idt are now invalid.
> > - * If you want to load them you must set up your own idt & gdt.
> > - */
> > - set_gdt(phys_to_virt(0),0);
> > - set_idt(phys_to_virt(0),0);
> > + if (image->preserve_cpu_ext) {
> > + /* The segment registers are funny things, they have
> > + * both a visible and an invisible part. Whenever the
> > + * visible part is set to a specific selector, the
> > + * invisible part is loaded with from a table in
> > + * memory. At no other time is the descriptor table
> > + * in memory accessed.
> > + *
> > + * I take advantage of this here by force loading the
> > + * segments, before I zap the gdt with an invalid
> > + * value.
> > + */
> > + load_segments();
> > + /* The gdt & idt are now invalid. If you want to load
> > + * them you must set up your own idt & gdt.
> > + */
> > + set_gdt(phys_to_virt(0), 0);
> > + set_idt(phys_to_virt(0), 0);
> > + }
>
> We can't keep the same idt and gdt as the pages they are on will be
> overwritten/reused. So explictily stomping on them sounds better
> so they never work. We can restore them on kernel reentry.
The original idea about this code is:
If the kexec image is claimed that it need not to "perserving extensive
CPU state" (such as FPU/MMX/GDT/LDT/IDT/CS/DS/ES/FS/GS/SS etc), the
IDT/GDT/CS/DS/ES/FS/GS/SS are not touched in kexec image code. So the
segment registers need not to be set.
But this is not clear. At least more description should be provided for
each preserve flag.
> > /* now call it */
> > - relocate_kernel((unsigned long)image->head, (unsigned long)page_list,
> > - image->start, cpu_has_pae);
> > + relocate_kernel_ptr((unsigned long)image->head,
> > + (unsigned long)page_list,
> > + image->start, cpu_has_pae);
>
> Why rename relocate_kernel?
> Ah. I see. You need to make it into a pointer again. The crazy don't
> stop the pgd support strikes again. It used to be named rnk.
You mean I should change the function pointer name to rnk to keep
consistency? I find rnk in IA64 implementation.
Best Regards,
Huang Ying
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm
