linuxsh-dev

Status of Kexec?

[Kristoffer E. <kri...@gm...>]

Paul, whats the status of kexec on the linuxsh tree? From what I recall it currently only works on x86 platforms, but the arm people seem eager to get it working on their platform also.

-- 
Kristoffer Ericson <Kri...@Gm...>

Re: Status of Kexec?

[Paul M. <le...@li...>]

On Sun, Sep 16, 2007 at 08:40:03PM -0700, Kristoffer Ericson wrote:
> Paul, whats the status of kexec on the linuxsh tree? From what I recall
> it currently only works on x86 platforms, but the arm people seem eager
> to get it working on their platform also.
> 
Huh? Kexec has run on plenty or architectures for a long time, including
sh. There aren't any problems with it that I know of, and plenty of
people are using it.

Re: Status of Kexec?

[Mike F. <va...@ge...>]

On Monday 17 September 2007, Paul Mundt wrote:
> On Sun, Sep 16, 2007 at 08:40:03PM -0700, Kristoffer Ericson wrote:
> > Paul, whats the status of kexec on the linuxsh tree? From what I recall
> > it currently only works on x86 platforms, but the arm people seem eager
> > to get it working on their platform also.
>
> Huh? Kexec has run on plenty or architectures for a long time, including
> sh. There aren't any problems with it that I know of, and plenty of
> people are using it.

if only the userland tools would get off their asses ...
-mike

Re: Status of Kexec?

[Paul M. <le...@li...>]

On Mon, Sep 17, 2007 at 06:02:46AM -0400, Mike Frysinger wrote:
> On Monday 17 September 2007, Paul Mundt wrote:
> > On Sun, Sep 16, 2007 at 08:40:03PM -0700, Kristoffer Ericson wrote:
> > > Paul, whats the status of kexec on the linuxsh tree? From what I recall
> > > it currently only works on x86 platforms, but the arm people seem eager
> > > to get it working on their platform also.
> >
> > Huh? Kexec has run on plenty or architectures for a long time, including
> > sh. There aren't any problems with it that I know of, and plenty of
> > people are using it.
> 
> if only the userland tools would get off their asses ...

http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary

is the tree to be using, the other ones are outdated and no longer
developed.

Re: Status of Kexec? (problem in sh3)

[Rafael I. Z. <riz...@ya...>]

--- Paul Mundt <le...@li...> wrote:
>
> On Mon, Sep 17, 2007 at 06:02:46AM -0400, Mike
> Frysinger wrote:
> > if only the userland tools would get off their
> asses ...
>
>
http://git.kernel.org/?p=linux/kernel/git/horms/kexec-tools-testing.git;a=summary
> 
> is the tree to be using, the other ones are outdated
> and no longer developed.

Hello, 
  I was trying kexec in sh3 (HP jornada 660lx:
SH7709 - HD64461) using those kexec-tools. But it gets
frozen when run "kexec -e". I would wish to know
what might be the issue.

Also, I used strace with "kexec -e" to see the last
reboot system call:

root@jornada6xx:~$ kexec -l /boot/zImage
--append="root=/dev/sda1 mem=32M"
root@jornada6xx:~$
root@jornada6xx:~$ kexec -f
kexec 1.101 released 15 February 2005
...
ADDRESS of empty_zero can be set SHELL environment
variable
KEXEC_EMPTY_ZERO as default
...
ADDRESS can be get in the following method in your
system.
..
3) CONFIG_MEMORY_START + CONFIG_ZERO_PAGE_OFFSET in
your kernel config file.
root@jornada6xx:~$


Well, The kernel (2.6.23-rc5 from jlime) was built
with 
CONFIG_MEMORY_START=0x0d000000
CONFIG_ZERO_PAGE_OFFSET=0x00001000
in the .config file. So i did:


root@jornada6xx:~$ export KEXEC_EMPTY_ZERO=0x0d001000
root@jornada6xx:~$ strace kexec -e
...
reboot(LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2,
0x45584543 /* LINUX_REBOOT_CMD_
??? */Starting new kernel
kexec information
  segment[0]: 0x0c001000 - 0x0c002000 (0x00001000)
  segment[1]: 0x0c210000 - 0x0c3b8000 (0x001a8000)
  start     : 0x8c210000

nothing else happened.

Regards,
Rafael


.



       
____________________________________________________________________________________
Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: mail, news, photos & more. 
http://mobile.yahoo.com/go?refer=1GNXIC

Re: Status of Kexec? (problem in sh3)

[Paul M. <le...@li...>]

On Wed, Oct 10, 2007 at 08:28:01AM -0700, Rafael Ignacio Zurita wrote:
>   I was trying kexec in sh3 (HP jornada 660lx:
> SH7709 - HD64461) using those kexec-tools. But it gets
> frozen when run "kexec -e". I would wish to know
> what might be the issue.
> 
kexec has not had any testing on SH-3 that I know of, so there are bound
to be bugs.

> root@jornada6xx:~$ export KEXEC_EMPTY_ZERO=0x0d001000
> root@jornada6xx:~$ strace kexec -e
> ...
> reboot(LINUX_REBOOT_MAGIC1, LINUX_REBOOT_MAGIC2,
> 0x45584543 /* LINUX_REBOOT_CMD_
> ??? */Starting new kernel
> kexec information
>   segment[0]: 0x0c001000 - 0x0c002000 (0x00001000)
>   segment[1]: 0x0c210000 - 0x0c3b8000 (0x001a8000)
>   start     : 0x8c210000
> 
> nothing else happened.

This comes from kexec_info(), the next step after this is the cache flush
and then jumping in to the new code. Thinking about this a bit,
flush_cache_all() on that particular SH-3 is a no-op, so you may have to
explicitly purge the region before doing the jump.

How does something like this work?

diff --git a/arch/sh/kernel/machine_kexec.c b/arch/sh/kernel/machine_kexec.c
index 5c17de5..ffd02b3 100644
--- a/arch/sh/kernel/machine_kexec.c
+++ b/arch/sh/kernel/machine_kexec.c
@@ -97,7 +97,8 @@ NORET_TYPE void machine_kexec(struct kimage *image)
 						relocate_new_kernel_size);
 
         kexec_info(image);
-	flush_cache_all();
+	__flush_purge_region((void *)reboot_code_buffer,
+			     relocate_new_kernel_size);
 
 	/* now call it */
 	rnk = (relocate_new_kernel_t) reboot_code_buffer;

Re: Status of Kexec? (problem in sh3)

[Rafael I. Z. <riz...@ya...>]

Hello Paul,

--- Paul Mundt <le...@li...> wrote:
> On Wed, Oct 10, 2007 at 08:28:01AM -0700, Rafael
> Ignacio Zurita wrote:
> >   I was trying kexec in sh3 ... But it
> > gets
> > frozen when run "kexec -e". I would wish to know
> > what might be the issue.
> > 
> kexec has not had any testing on SH-3 that I know
> of, so there are bound
> to be bugs.
> 
> This comes from kexec_info(), the next step after
> this is the cache flush
> and then jumping in to the new code. Thinking about
> this a bit,
> flush_cache_all() on that particular SH-3 is a
> no-op, so you may have to
> explicitly purge the region before doing the jump.
> 
> How does something like this work?

No luck... I applied the patch, but it gave me
the same system frozen after "kexec -e".
If you need some useful information to help with
this problem i will test.

Thanks in advance,
Rafael


> diff --git a/arch/sh/kernel/machine_kexec.c
> b/arch/sh/kernel/machine_kexec.c
> index 5c17de5..ffd02b3 100644
> --- a/arch/sh/kernel/machine_kexec.c
> +++ b/arch/sh/kernel/machine_kexec.c
> @@ -97,7 +97,8 @@ NORET_TYPE void
> machine_kexec(struct kimage *image)
>  					relocate_new_kernel_size);
>  
>          kexec_info(image);
> -	flush_cache_all();
> +	__flush_purge_region((void *)reboot_code_buffer,
> +			     relocate_new_kernel_size);
>  
>  	/* now call it */
>  	rnk = (relocate_new_kernel_t) reboot_code_buffer;
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com