How to implement kexec on e500 ?

How to implement kexec on e500 ?

[wilbur.chan]

kernel 2.6.21.7

As we know , kexec stores  data  for new kernel image ,  in the form
of   a page list.

And kexec uses the physical address of the another  page for a
"next-page" pointer.

However, PowerPC e500  does not allow users to turn off the MMU, so we
can not used physical address directly in our code.


Someone suggested that changing  relocate_kernel.S to add a TLB 1-to-1
mapping of DRAM .

What does "mapping" mean ?

Any suggestion to implement kexec on e500 ?



Cheers,

wilbur

Re: How to implement kexec on e500 ?

[Kumar Gala]

On Jun 29, 2009, at 8:47 AM, wilbur.chan wrote:

> kernel 2.6.21.7
>
> As we know , kexec stores  data  for new kernel image ,  in the form
> of   a page list.
>
> And kexec uses the physical address of the another  page for a
> "next-page" pointer.
>
> However, PowerPC e500  does not allow users to turn off the MMU, so we
> can not used physical address directly in our code.
>
>
> Someone suggested that changing  relocate_kernel.S to add a TLB 1-to-1
> mapping of DRAM .
>
> What does "mapping" mean ?
>
> Any suggestion to implement kexec on e500 ?

Wilbur, kexec has been implemented on e500.  There are some patches on  
the list for this and they just need to be respun and reviewed again.

- k

Re: How to implement kexec on e500 ?

[wilbur.chan]

Excuse me ,

btw,how to search these patches on this maillist?

through Linuxppc-dev Archives one by one?

Cheers,

wilbur

2009/6/29, Kumar Gala <galak@kernel.crashing.org>:
>
> On Jun 29, 2009, at 8:47 AM, wilbur.chan wrote:
>
>> kernel 2.6.21.7
>>
>> As we know , kexec stores  data  for new kernel image ,  in the form
>> of   a page list.
>>
>> And kexec uses the physical address of the another  page for a
>> "next-page" pointer.
>>
>> However, PowerPC e500  does not allow users to turn off the MMU, so we
>> can not used physical address directly in our code.
>>
>>
>> Someone suggested that changing  relocate_kernel.S to add a TLB 1-to-1
>> mapping of DRAM .
>>
>> What does "mapping" mean ?
>>
>> Any suggestion to implement kexec on e500 ?
>
> Wilbur, kexec has been implemented on e500.  There are some patches on
> the list for this and they just need to be respun and reviewed again.
>
> - k
>

Re: How to implement kexec on e500 ?

[kernel mailz]

Did some searching on the archieve

Looks like this is a old patch
[PATCH 03/10] powerpc: Add kexec support for PPC_85xx platforms
Dale Farnsworth
Thu, 22 Nov 2007 07:51:52 -0800

Is this the patch you were referring to kumar

-TZ


On Mon, Jun 29, 2009 at 9:06 PM, wilbur.chan<wilbur512@gmail.com> wrote:
> Excuse me ,
>
> btw,how to search these patches on this maillist?
>
> through Linuxppc-dev Archives one by one?
>
> Cheers,
>
> wilbur
>
> 2009/6/29, Kumar Gala <galak@kernel.crashing.org>:
>>
>> On Jun 29, 2009, at 8:47 AM, wilbur.chan wrote:
>>
>>> kernel 2.6.21.7
>>>
>>> As we know , kexec stores =A0data =A0for new kernel image , =A0in the f=
orm
>>> of =A0 a page list.
>>>
>>> And kexec uses the physical address of the another =A0page for a
>>> "next-page" pointer.
>>>
>>> However, PowerPC e500 =A0does not allow users to turn off the MMU, so w=
e
>>> can not used physical address directly in our code.
>>>
>>>
>>> Someone suggested that changing =A0relocate_kernel.S to add a TLB 1-to-=
1
>>> mapping of DRAM .
>>>
>>> What does "mapping" mean ?
>>>
>>> Any suggestion to implement kexec on e500 ?
>>
>> Wilbur, kexec has been implemented on e500. =A0There are some patches on
>> the list for this and they just need to be respun and reviewed again.
>>
>> - k
>>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>